From: Jens Axboe <axboe@kernel•dk>
To: Christoph Hellwig <hch@lst•de>
Cc: "Ed L. Cashin" <ed.cashin@acm•org>,
Geoff Levand <geoff@infradead•org>,
Maxim Levitsky <maximlevitsky@gmail•com>,
linux-block@vger•kernel.org, linuxppc-dev@lists•ozlabs.org,
linux-mtd@lists•infradead.org, sparclinux@vger•kernel.org
Subject: Re: make a few block drivers highmem safe
Date: Fri, 11 May 2018 15:08:26 -0600 [thread overview]
Message-ID: <e5f3ffef-4fa3-50d3-4fbe-d67ba2a85bd8@kernel.dk> (raw)
In-Reply-To: <20180509135948.20329-1-hch@lst.de>
On 5/9/18 7:59 AM, Christoph Hellwig wrote:
> Hi all,
>
> this series converts a few random block drivers to be highmem safe,
> in preparation of eventually getting rid of the block layer bounce
> buffering support.
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2018-05-11 21:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 13:59 make a few block drivers highmem safe Christoph Hellwig
2018-05-09 13:59 ` [PATCH 1/7] mtip32xx: don't use block layer bounce buffers Christoph Hellwig
2018-05-09 15:17 ` Johannes Thumshirn
2018-05-09 13:59 ` [PATCH 2/7] DAC960: " Christoph Hellwig
2018-05-09 15:17 ` Johannes Thumshirn
2018-05-09 13:59 ` [PATCH 3/7] memstick: don't call blk_queue_bounce_limit Christoph Hellwig
2018-05-09 13:59 ` [PATCH 4/7] mtd_blkdevs: handle highmem pages Christoph Hellwig
2018-05-09 13:59 ` [PATCH 5/7] aoe: " Christoph Hellwig
2018-05-09 13:59 ` [PATCH 6/7] jsflash: " Christoph Hellwig
2018-05-09 13:59 ` [PATCH 7/7] ps3disk: " Christoph Hellwig
2018-05-09 16:26 ` make a few block drivers highmem safe Jens Axboe
2018-05-11 21:08 ` 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=e5f3ffef-4fa3-50d3-4fbe-d67ba2a85bd8@kernel.dk \
--to=axboe@kernel$(echo .)dk \
--cc=ed.cashin@acm$(echo .)org \
--cc=geoff@infradead$(echo .)org \
--cc=hch@lst$(echo .)de \
--cc=linux-block@vger$(echo .)kernel.org \
--cc=linux-mtd@lists$(echo .)infradead.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=maximlevitsky@gmail$(echo .)com \
--cc=sparclinux@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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