From: Jens Axboe <jens.axboe@oracle.com>
To: Tejun Heo <tj@kernel.org>
Cc: bharrosh@panasas.com, linux-kernel@vger.kernel.org,
fujita.tomonori@lab.ntt.co.jp
Subject: Re: [GIT PATCH block#for-linus] block: various fixes
Date: Wed, 15 Apr 2009 18:15:51 +0200 [thread overview]
Message-ID: <20090415161550.GO5178@kernel.dk> (raw)
In-Reply-To: <1239801027-9201-1-git-send-email-tj@kernel.org>
On Wed, Apr 15 2009, Tejun Heo wrote:
> Hello,
>
> This patchset contains the following five block related fix patches.
>
> 0001-scatterlist-make-sure-sg_miter_next-doesn-t-retur.patch
> 0002-block-fix-SG_IO-vector-request-data-length-handling.patch
> 0003-block-fix-queue-bounce-limit-setting.patch
> 0004-bio-fix-bio_kmalloc.patch
> 0005-bio-use-bio_kmalloc-in-copy-map-functions.patch
>
> 0001-0003 are unchanged re-posting of the first three patches of
> blk-map-related-fixes[1]. The fourth patch of the previous patchset
> is dropped and 0004 reimplements bio_kmalloc() as per Jens'
> suggestion. 0005 is new and uses bio_kmalloc() in the map functions.
>
> This patchset is also available in the following git tree.
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc.git blk-fixes
>
> and contains the following changes.
Thanks a lot, Tejun! I'll add these and include them in the next 2.6.30
push.
--
Jens Axboe
prev parent reply other threads:[~2009-04-15 16:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 13:10 [GIT PATCH block#for-linus] block: various fixes Tejun Heo
2009-04-15 13:10 ` [PATCH 1/5] scatterlist: make sure sg_miter_next() doesn't return 0 sized mappings Tejun Heo
2009-04-15 13:10 ` [PATCH 2/5] block: fix SG_IO vector request data length handling Tejun Heo
2009-04-15 13:10 ` [PATCH 3/5] block: fix queue bounce limit setting Tejun Heo
2009-04-15 13:10 ` [PATCH 4/5] bio: fix bio_kmalloc() Tejun Heo
2009-04-15 13:10 ` [PATCH 5/5] bio: use bio_kmalloc() in copy/map functions Tejun Heo
2009-04-15 16:15 ` 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=20090415161550.GO5178@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=bharrosh@panasas.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox