linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: hch@infradead.org (Christoph Hellwig)
Subject: [GIT PULL] nvme fixes for 4.20
Date: Fri, 9 Nov 2018 05:20:12 -0800	[thread overview]
Message-ID: <20181109132011.GA2706@infradead.org> (raw)
In-Reply-To: <6b8d8562-a31d-bf11-557b-7f33a17d6e60@kernel.dk>

On Fri, Nov 09, 2018@06:16:09AM -0700, Jens Axboe wrote:
> On 11/8/18 11:56 PM, Christoph Hellwig wrote:
> >  - revert an RDMA commit that didn't help but caused problems
> >  - fix another minor P2P fallout
> >  - make sure the multipath device inherits the devices limits of
> >    the controllers below
> > 
> > The following changes since commit 651022382c7f8da46cb4872a545ee1da6d097d2a:
> > 
> >   Linux 4.20-rc1 (2018-11-04 15:37:52 -0800)
> > 
> > are available in the Git repository at:
> > 
> >   git://git.infradead.org/nvme.git nvme-4.20
> 
> This is based on 4.20-rc1 for some reason, not my for-linus. So I get
> a few thousand extra commits... I pulled the patches and applied
> manually.

That is because your for-linus was still 4.20-rc based when
I created it.

  reply	other threads:[~2018-11-09 13:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-09  6:56 [GIT PULL] nvme fixes for 4.20 Christoph Hellwig
2018-11-09 13:16 ` Jens Axboe
2018-11-09 13:20   ` Christoph Hellwig [this message]
2018-11-09 13:29     ` Jens Axboe
2018-11-09 17:10       ` Sagi Grimberg
2018-11-09 17:12         ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2018-12-07 15:38 Christoph Hellwig
2018-12-07 15:40 ` Jens Axboe
2018-11-30 15:24 Christoph Hellwig
2018-11-30 15:26 ` Jens Axboe
2018-11-30 15:37   ` Keith Busch
2018-11-30 16:26   ` Christoph Hellwig
2018-11-30 17:12     ` Jens Axboe
2018-11-02  6:37 Christoph Hellwig
2018-11-02 14:15 ` 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=20181109132011.GA2706@infradead.org \
    --to=hch@infradead.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;
as well as URLs for NNTP newsgroup(s).