From: John Garry <john.garry@huawei.com>
To: Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
Keith Busch <keith.busch@intel.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
fin4478 fin4478 <fin4478@hotmail.com>,
Dou Liyang <douliyangs@gmail.com>,
Thomas Gleixner <tglx@linutronix.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: Tue, 15 Jan 2019 09:12:53 +0000 [thread overview]
Message-ID: <4893cfbb-f2db-cec5-e5b8-68e836d243f1@huawei.com> (raw)
In-Reply-To: <a97735d4-b82b-d09f-7729-0e74d95475c9@kernel.dk>
On 14/01/2019 18:05, Jens Axboe wrote:
> On 1/14/19 11:05 AM, Christoph Hellwig wrote:
>> On Mon, Jan 14, 2019 at 11:02:07AM -0700, Keith Busch wrote:
>>> 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?
>>
>> It is in my local queue for -rc3 already.
>
Any chance we could have this included in linux-next?
Cheers
> Great, thanks.
>
prev parent reply other threads:[~2019-01-15 9:13 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
2019-01-14 18:05 ` Christoph Hellwig
2019-01-14 18:05 ` Jens Axboe
2019-01-15 9:12 ` John Garry [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=4893cfbb-f2db-cec5-e5b8-68e836d243f1@huawei.com \
--to=john.garry@huawei.com \
--cc=axboe@kernel.dk \
--cc=bhelgaas@google.com \
--cc=douliyangs@gmail.com \
--cc=fin4478@hotmail.com \
--cc=hch@lst.de \
--cc=keith.busch@intel.com \
--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