Linux block layer
 help / color / mirror / Atom feed
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 updates for Linux 4.20
Date: Fri, 19 Oct 2018 09:48:14 -0600	[thread overview]
Message-ID: <9d8b9b42-5d2f-7f9a-0cd6-4e14e136f817@kernel.dk> (raw)
In-Reply-To: <20181019153539.GA24842@infradead.org>

On 10/19/18 9:35 AM, Christoph Hellwig wrote:
> The second batch of updates for Linux 4.20:
>  - lot of fixes for issues found by static type checkers from Bart
>  - two small fixes from Keith
>  - fabrics cleanups in preparation of the TCP transport from Sagi
>  - more cleanups from Chaitanya

Pulled, thanks.

-- 
Jens Axboe

      reply	other threads:[~2018-10-19 15:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-19 15:35 [GIT PULL] nvme updates for Linux 4.20 Christoph Hellwig
2018-10-19 15:48 ` 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=9d8b9b42-5d2f-7f9a-0cd6-4e14e136f817@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