From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>
Cc: Keith Busch <keith.busch@intel.com>,
linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org
Subject: Re: [GIT PULL] nvme fixes for Linux 4.14-rc4
Date: Thu, 5 Oct 2017 10:45:12 -0600 [thread overview]
Message-ID: <8f1e6bc2-f511-7209-bc28-3876ed806755@kernel.dk> (raw)
In-Reply-To: <20171005163654.walnk7642obfyjp6@infradead.org>
On 10/05/2017 10:36 AM, Christoph Hellwig wrote:
> A trivial one-liner from Martin to fix the visible of the uuid attr,
> and another one (originally from Abhishek Shah, rewritten by me) to
> fix the CMB addresses passed back to the controller in case of a system
> that remaps BAR addresses between host and device.
>
> The following changes since commit a5f3d8a5eaaf917878f07998e6f1ea46024e6bab:
>
> bcache: use llist_for_each_entry_safe() in __closure_wake_up() (2017-09-27 14:54:49 -0600)
>
> are available in the git repository at:
>
> git://git.infradead.org/nvme.git nvme-4.14
>
> for you to fetch changes up to 8969f1f8291762c13147c1ba89d46238af01675b:
>
> nvme-pci: Use PCI bus address for data/queues in CMB (2017-10-04 11:42:53 +0200)
>
> ----------------------------------------------------------------
> Christoph Hellwig (1):
> nvme-pci: Use PCI bus address for data/queues in CMB
>
> Martin Wilck (1):
> nvme: fix visibility of "uuid" ns attribute
Pulled, thanks.
--
Jens Axboe
prev parent reply other threads:[~2017-10-05 16:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 16:36 [GIT PULL] nvme fixes for Linux 4.14-rc4 Christoph Hellwig
2017-10-05 16:45 ` 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=8f1e6bc2-f511-7209-bc28-3876ed806755@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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