From: Jens Axboe <jens.axboe@oracle.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: linux-scsi@vger.kernel.org, dougg@torque.net,
michaelc@cs.wisc.edu, James.Bottomley@HansenPartnership.com
Subject: Re: [PATCH 0/8] sg cleanup patches after the block conversion
Date: Tue, 9 Sep 2008 15:42:35 +0200 [thread overview]
Message-ID: <20080909134235.GN20055@kernel.dk> (raw)
In-Reply-To: <20080909223555K.fujita.tomonori@lab.ntt.co.jp>
On Tue, Sep 09 2008, FUJITA Tomonori wrote:
> On Tue, 2 Sep 2008 22:50:00 +0900
> FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> wrote:
>
> > Here's some cleanup patches, removing functions that became
> > unnecessary after the block conversion, functions used temporally
> > during the conversion, etc.
> >
> > This is against the for-2.6.28 brach in the block tree:
>
> Jens, can you apply this to your for-2.6.28?
Certainly, I thought I already had...
--
Jens Axboe
prev parent reply other threads:[~2008-09-09 13:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 13:50 [PATCH 0/8] sg cleanup patches after the block conversion FUJITA Tomonori
2008-09-02 13:50 ` [PATCH 1/8] sg: rename sg_cmd_done sg_rq_end_io FUJITA Tomonori
2008-09-02 13:50 ` [PATCH 2/8] sg: remove SG_ALLOW_DIO_CODE define FUJITA Tomonori
2008-09-02 13:50 ` [PATCH 3/8] sg: remove b_malloc_len in sg_scatter_hold struct FUJITA Tomonori
2008-09-02 13:50 ` [PATCH 4/8] sg: remove __sg_start_req FUJITA Tomonori
2008-09-02 13:50 ` [PATCH 5/8] sg: incorporate sg_build_direct into sg_start_req FUJITA Tomonori
2008-09-02 13:50 ` [PATCH 6/8] sg: remove sg_write_xfer FUJITA Tomonori
2008-09-02 13:50 ` [PATCH 7/8] sg: remove sg_read_xfer FUJITA Tomonori
2008-09-02 13:50 ` [PATCH 8/8] sg: remove unnecessary blk_rq_unmap_user FUJITA Tomonori
2008-09-09 13:35 ` [PATCH 0/8] sg cleanup patches after the block conversion FUJITA Tomonori
2008-09-09 13:42 ` Jens Axboe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080909134235.GN20055@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=dougg@torque.net \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.