All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>
Cc: Keith Busch <keith.busch@intel.com>,
	Sagi Grimberg <sagi@grimberg.me>,
	linux-nvme@lists.infradead.org, linux-block@vger.kernel.org
Subject: Re: [GIT PULL] nvme updates for 5.3
Date: Mon, 24 Jun 2019 10:11:26 -0600	[thread overview]
Message-ID: <00f87f06-99f3-b28d-eef8-d6bb8afe2f72@kernel.dk> (raw)
In-Reply-To: <20190624061241.GA31634@infradead.org>

On 6/24/19 12:12 AM, Christoph Hellwig wrote:
> A large chunk of NVMe updates for 5.3.  Highlights:
> 
>   - improved PCIe suspent support (Keith Busch)
>   - error injection support for the admin queue (Akinobu Mita)
>   - Fibre Channel discovery improvements (James Smart)
>   - tracing improvements including nvmetc tracing support (Minwoo Im)
>   - misc fixes and cleanups (Anton Eidelman, Minwoo Im, Chaitanya Kulkarni)
> 
> 
> The following changes since commit 474a280036e8d319ef852f1dec59bedf4eda0107:
> 
>    cgroup: export css_next_descendant_pre for bfq (2019-06-21 02:48:34 -0600)
> 
> are available in the Git repository at:
> 
>    git://git.infradead.org/nvme.git nvme-5.3

Pulled, thanks.

-- 
Jens Axboe


WARNING: multiple messages have this Message-ID (diff)
From: axboe@kernel.dk (Jens Axboe)
Subject: [GIT PULL] nvme updates for 5.3
Date: Mon, 24 Jun 2019 10:11:26 -0600	[thread overview]
Message-ID: <00f87f06-99f3-b28d-eef8-d6bb8afe2f72@kernel.dk> (raw)
In-Reply-To: <20190624061241.GA31634@infradead.org>

On 6/24/19 12:12 AM, Christoph Hellwig wrote:
> A large chunk of NVMe updates for 5.3.  Highlights:
> 
>   - improved PCIe suspent support (Keith Busch)
>   - error injection support for the admin queue (Akinobu Mita)
>   - Fibre Channel discovery improvements (James Smart)
>   - tracing improvements including nvmetc tracing support (Minwoo Im)
>   - misc fixes and cleanups (Anton Eidelman, Minwoo Im, Chaitanya Kulkarni)
> 
> 
> The following changes since commit 474a280036e8d319ef852f1dec59bedf4eda0107:
> 
>    cgroup: export css_next_descendant_pre for bfq (2019-06-21 02:48:34 -0600)
> 
> are available in the Git repository at:
> 
>    git://git.infradead.org/nvme.git nvme-5.3

Pulled, thanks.

-- 
Jens Axboe

  reply	other threads:[~2019-06-24 16:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-24  6:12 [GIT PULL] nvme updates for 5.3 Christoph Hellwig
2019-06-24  6:12 ` Christoph Hellwig
2019-06-24 16:11 ` Jens Axboe [this message]
2019-06-24 16:11   ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2019-07-11 11:20 Christoph Hellwig
2019-07-11 11:20 ` Christoph Hellwig
2019-07-11 14:13 ` Jens Axboe
2019-07-11 14:13   ` Jens Axboe

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=00f87f06-99f3-b28d-eef8-d6bb8afe2f72@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 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.