From: Keith Busch <keith.busch@intel.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: fin4478 fin4478 <fin4478@hotmail.com>,
Dou Liyang <douliyangs@gmail.com>, Jens Axboe <axboe@kernel.dk>,
Thomas Gleixner <tglx@linutronix.de>,
Christoph Hellwig <hch@lst.de>,
linux-pci@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ming Lei <ming.lei@redhat.com>,
linux-nvme@lists.infradead.org
Subject: Re: Please remove warnings from msi.c:1269 and blk-mq-pci.c:52 some day
Date: Mon, 14 Jan 2019 11:02:07 -0700 [thread overview]
Message-ID: <20190114180207.GC27149@localhost.localdomain> (raw)
In-Reply-To: <20190114170338.GA27149@localhost.localdomain>
[+linux-nvme@lists.infradead.org]
On Mon, Jan 14, 2019 at 10:03:39AM -0700, Keith Busch wrote:
> [+Ming]
> On Mon, Jan 14, 2019 at 08:31:45AM -0600, Bjorn Helgaas wrote:
> > [+cc Dou, Jens, Thomas, Christoph, linux-pci, LKML]
> >
> > On Sun, Jan 13, 2019 at 11:24 PM fin4478 fin4478 <fin4478@hotmail.com> wrote:
> > >
> > > Hi,
> > >
> > > A regression from the 4.20 kernel: I have the Asgard 256GB nvme drive
> > > and my custom non debug 1000Hz timer kernel 5.0 started to throw a
> > > couple of warning messages at boot. My system works ok:
>
> I think Ming's patch here fixes this:
>
> http://lists.infradead.org/pipermail/linux-nvme/2019-January/021902.html
User fin4478 <fin4478@hotmail.com> informs me Ming's patch above fixes
the warnings, but responding to the mailing lists from that email account
are blocked for "security or policy reasons" and requested I forward
the successful test result.
Christoph, Jens: may we queue this up for -rc3?
next prev parent reply other threads:[~2019-01-14 18:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AM0PR06MB3969BE1DFD53EFF6228E1A0AA1800@AM0PR06MB3969.eurprd06.prod.outlook.com>
2019-01-14 14:31 ` Please remove warnings from msi.c:1269 and blk-mq-pci.c:52 some day Bjorn Helgaas
2019-01-14 17:03 ` Keith Busch
2019-01-14 18:02 ` Keith Busch [this message]
2019-01-14 18:05 ` Christoph Hellwig
2019-01-14 18:05 ` Jens Axboe
2019-01-15 9:12 ` John Garry
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=20190114180207.GC27149@localhost.localdomain \
--to=keith.busch@intel.com \
--cc=axboe@kernel.dk \
--cc=bhelgaas@google.com \
--cc=douliyangs@gmail.com \
--cc=fin4478@hotmail.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=tglx@linutronix.de \
/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