From: Jens Axboe <axboe@kernel.dk>
To: Guenter Roeck <linux@roeck-us.net>, Ming Lei <ming.lei@redhat.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>, Omar Sandoval <osandov@fb.com>
Subject: Re: linux-next: Tree for Jan 16
Date: Thu, 17 Jan 2019 11:34:01 -0700 [thread overview]
Message-ID: <10619062-9531-e843-1620-7518e27583f8@kernel.dk> (raw)
In-Reply-To: <20190117183254.GA17361@roeck-us.net>
On 1/17/19 11:32 AM, Guenter Roeck wrote:
> On Thu, Jan 17, 2019 at 06:35:55PM +0800, Ming Lei wrote:
>>>
>>> Hi Guenter,
>>>
>>> Could you share me the .config?
>>
> Any 32 bit configuration from affected architectures should work.
>
>> From your dmesg log, looks the test is run on i386, so please
>> feel free to try the following patch:
>>
>> https://marc.info/?l=linux-kernel&m=154772088110800&w=2
>>
> Is this still relevant ? Today's image is fine.
The patches were pulled, I think Ming would still appreciate it if
you could test the previous tree with that patch on top.
--
Jens Axboe
next prev parent reply other threads:[~2019-01-17 18:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 6:38 linux-next: Tree for Jan 16 Stephen Rothwell
2019-01-16 17:00 ` linux-next: Tree for Jan 16 (PCI config warning?) Randy Dunlap
2019-01-16 17:23 ` Sinan Kaya
2019-01-16 18:06 ` Randy Dunlap
2019-01-16 20:35 ` linux-next: Tree for Jan 16 Guenter Roeck
2019-01-17 8:49 ` Ming Lei
2019-01-17 10:35 ` Ming Lei
2019-01-17 18:32 ` Guenter Roeck
2019-01-17 18:34 ` Jens Axboe [this message]
2019-01-17 21:35 ` Guenter Roeck
-- strict thread matches above, loose matches on Subject: below --
2023-01-16 4:17 Stephen Rothwell
2022-01-16 4:06 Stephen Rothwell
2020-01-16 9:17 Stephen Rothwell
2018-01-16 5:23 Stephen Rothwell
2017-01-16 4:21 Stephen Rothwell
2015-01-16 8:47 Stephen Rothwell
2014-01-16 6:56 Stephen Rothwell
2013-01-16 4:24 Stephen Rothwell
2012-01-16 2:57 Stephen Rothwell
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=10619062-9531-e843-1620-7518e27583f8@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=ming.lei@redhat.com \
--cc=osandov@fb.com \
--cc=sfr@canb.auug.org.au \
/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).