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 <kbusch@kernel.org>,
	linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
	linux-nvme@lists.infradead.org
Subject: Re: [GIT PULL] second round of nvme updates for 5.12
Date: Thu, 11 Feb 2021 11:34:23 -0700	[thread overview]
Message-ID: <06daa8d8-3ec9-8372-f912-65e844b87e31@kernel.dk> (raw)
In-Reply-To: <20210211183316.GA2527859@infradead.org>

On 2/11/21 11:33 AM, Christoph Hellwig wrote:
> On Thu, Feb 11, 2021 at 11:31:58AM -0700, Jens Axboe wrote:
>> On 2/11/21 11:15 AM, Christoph Hellwig wrote:
>>> Note that we have some issues with the previous updates.  We're working
>>> fast on fixes for those, but in the meantime I think it is good to get
>>> these changes out to you and into linux-next.
>>
>> Pulled - it throws a trivial reject in the quirks list, fwiw.
> 
> Yes, people are producing buggy controllers way to quickly.. :(

We'll do whitelists instead next time, less churn ;-)

-- 
Jens Axboe


WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>
Cc: Keith Busch <kbusch@kernel.org>,
	linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
	linux-nvme@lists.infradead.org
Subject: Re: [GIT PULL] second round of nvme updates for 5.12
Date: Thu, 11 Feb 2021 11:34:23 -0700	[thread overview]
Message-ID: <06daa8d8-3ec9-8372-f912-65e844b87e31@kernel.dk> (raw)
In-Reply-To: <20210211183316.GA2527859@infradead.org>

On 2/11/21 11:33 AM, Christoph Hellwig wrote:
> On Thu, Feb 11, 2021 at 11:31:58AM -0700, Jens Axboe wrote:
>> On 2/11/21 11:15 AM, Christoph Hellwig wrote:
>>> Note that we have some issues with the previous updates.  We're working
>>> fast on fixes for those, but in the meantime I think it is good to get
>>> these changes out to you and into linux-next.
>>
>> Pulled - it throws a trivial reject in the quirks list, fwiw.
> 
> Yes, people are producing buggy controllers way to quickly.. :(

We'll do whitelists instead next time, less churn ;-)

-- 
Jens Axboe


_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  reply	other threads:[~2021-02-11 18:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-11 18:15 [GIT PULL] second round of nvme updates for 5.12 Christoph Hellwig
2021-02-11 18:15 ` Christoph Hellwig
2021-02-11 18:31 ` Jens Axboe
2021-02-11 18:31   ` Jens Axboe
2021-02-11 18:33   ` Christoph Hellwig
2021-02-11 18:33     ` Christoph Hellwig
2021-02-11 18:34     ` Jens Axboe [this message]
2021-02-11 18:34       ` 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=06daa8d8-3ec9-8372-f912-65e844b87e31@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=hch@infradead.org \
    --cc=kbusch@kernel.org \
    --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.