i2o_scsi_reply(9) [suse man page]

I2O_SCSI_REPLY(9)					       Message-based devices						 I2O_SCSI_REPLY(9)

NAME

       i2o_scsi_reply - SCSI OSM message reply handler

SYNOPSIS

       int i2o_scsi_reply(struct i2o_controller * c, u32 m, struct i2o_message * msg);

ARGUMENTS

       c
	   controller issuing the reply

       m
	   message id for flushing

       msg
	   the message from the controller

DESCRIPTION

       Process reply messages (interrupts in normal scsi controller think). We can get a variety of messages to process. The normal path is scsi
       command completions. We must also deal with IOP failures, the reply to a bus reset and the reply to a LUN query.

       Returns 0 on success and if the reply should not be flushed or > 0 on success and if the reply should be flushed. Returns negative error
       code on failure and if the reply should be flushed.

COPYRIGHT

Kernel Hackers Manual 2.6.					     July 2010							 I2O_SCSI_REPLY(9)

xcb_randr_get_crtc_gamma(3)					   XCB Requests 				       xcb_randr_get_crtc_gamma(3)

NAME

       xcb_randr_get_crtc_gamma -

SYNOPSIS

       #include <xcb/randr.h>

   Request function
       xcb_randr_get_crtc_gamma_cookie_t xcb_randr_get_crtc_gamma(xcb_connection_t *conn, xcb_randr_crtc_t crtc);

   Reply datastructure
       typedef struct xcb_randr_get_crtc_gamma_reply_t {
	   uint8_t  response_type;
	   uint8_t  pad0;
	   uint16_t sequence;
	   uint32_t length;
	   uint16_t size;
	   uint8_t  pad1[22];
       } xcb_randr_get_crtc_gamma_reply_t;

   Reply function
       xcb_randr_get_crtc_gamma_reply_t *xcb_randr_get_crtc_gamma_reply(xcb_connection_t *conn, xcb_randr_get_crtc_gamma_cookie_t cookie,
	      xcb_generic_error_t **e);

   Reply accessors
       uint16_t *xcb_randr_get_crtc_gamma_red(const xcb_randr_get_crtc_gamma_request_t *reply);

       int xcb_randr_get_crtc_gamma_red_length(const xcb_randr_get_crtc_gamma_reply_t *reply);

       xcb_generic_iterator_t xcb_randr_get_crtc_gamma_red_end(const xcb_randr_get_crtc_gamma_reply_t *reply);

       uint16_t *xcb_randr_get_crtc_gamma_green(const xcb_randr_get_crtc_gamma_request_t *reply);

       int xcb_randr_get_crtc_gamma_green_length(const xcb_randr_get_crtc_gamma_reply_t *reply);

       xcb_generic_iterator_t xcb_randr_get_crtc_gamma_green_end(const xcb_randr_get_crtc_gamma_reply_t *reply);

       uint16_t *xcb_randr_get_crtc_gamma_blue(const xcb_randr_get_crtc_gamma_request_t *reply);

       int xcb_randr_get_crtc_gamma_blue_length(const xcb_randr_get_crtc_gamma_reply_t *reply);

       xcb_generic_iterator_t xcb_randr_get_crtc_gamma_blue_end(const xcb_randr_get_crtc_gamma_reply_t *reply);

REQUEST ARGUMENTS

       conn	 The XCB connection to X11.

       crtc	 TODO: NOT YET DOCUMENTED.

REPLY FIELDS

       response_type
		 The type of this reply, in this case XCB_RANDR_GET_CRTC_GAMMA. This field is also present in the xcb_generic_reply_t and can be
		 used to tell replies apart from each other.

       sequence  The sequence number of the last request processed by the X11 server.

       length	 The length of the reply, in words (a word is 4 bytes).

       size	 TODO: NOT YET DOCUMENTED.

DESCRIPTION

RETURN VALUE

       Returns an xcb_randr_get_crtc_gamma_cookie_t. Errors have to be handled when calling the reply function xcb_randr_get_crtc_gamma_reply.

       If you want to handle errors in the event loop instead, use xcb_randr_get_crtc_gamma_unchecked. See xcb-requests(3) for details.

ERRORS

       This request does never generate any errors.

SEE ALSO

AUTHOR

       Generated from randr.xml. Contact xcb@lists.freedesktop.org for corrections and improvements.

XCB
								    2014-06-10					       xcb_randr_get_crtc_gamma(3)