On Sun, Jun 19 2005, Christoph Hellwig wrote: > @@ -2098,14 +2098,14 @@ > * Data will be mapped directly for zero copy io, if possible. Otherwise > * a kernel bounce buffer is used. > * > - * A matching blk_rq_unmap_user() must be issued at the end of io, while > - * still in process context. > + * A matching blk_rq_unmap_user_iov() must be issued at the end of io, > + * while still in process context. ? > * Note: The mapped bio may need to be bounced through blk_queue_bounce() > * before being submitted to the device, as pages mapped may be out of > * reach. It's the callers responsibility to make sure this happens. The > - * original bio must be passed back in to blk_rq_unmap_user() for proper > - * unmapping. > + * original bio must be passed back in to blk_rq_unmap_user_iov() for > + * proper unmapping. > */ Ditto > @@ -2221,9 +2220,10 @@ > /** > * blk_rq_map_kern - map kernel data to a request, for REQ_BLOCK_PC usage > * @q: request queue where request should be inserted > - * @rw: READ or WRITE data > + * @rw: request to fill @rq Rest looks good, care to rediff it? -- Jens Axboe - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
