From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: Tuowen Zhao <ztuowen@gmail.com>,
linux-kernel@vger.kernel.org, mika.westerberg@linux.intel.com,
acelan.kao@canonical.com, mcgrof@kernel.org, davem@davemloft.net
Subject: Re: [PATCH v5 0/4] Fix MTRR bug for intel-lpss-pci
Date: Thu, 17 Oct 2019 11:04:00 +0300 [thread overview]
Message-ID: <20191017080400.GE32742@smile.fi.intel.com> (raw)
In-Reply-To: <20191017073116.GM4365@dell>
On Thu, Oct 17, 2019 at 08:31:16AM +0100, Lee Jones wrote:
> On Thu, 17 Oct 2019, Andy Shevchenko wrote:
> > On Wed, Oct 16, 2019 at 03:06:25PM -0600, Tuowen Zhao wrote:
> > > Some BIOS erroneously specifies write-combining BAR for intel-lpss-pci
> > > in MTRR. This will cause the system to hang during boot. If possible,
> > > this bug could be corrected with a firmware update.
> > >
> > > Previous version: https://lkml.org/lkml/2019/10/14/575
> > >
> > > Changes from previous version:
> > >
> > > * implement ioremap_uc for sparc64
> > > * split docs changes to not CC stable (doc location moved since 5.3)
> > >
> >
> > It forgot to explicitly mention through which tree is supposed to go.
> > I think it's MFD one, correct?
>
> To be fair, that's not really up to the submitter to decide.
Submitter still can share their view, no?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2019-10-17 8:04 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 21:06 [PATCH v5 0/4] Fix MTRR bug for intel-lpss-pci Tuowen Zhao
2019-10-16 21:06 ` [PATCH v5 1/4] sparc64: implement ioremap_uc Tuowen Zhao
2019-10-16 21:20 ` David Miller
2019-10-28 20:46 ` Fwd: " Tuowen Zhao
2019-10-28 23:09 ` David Miller
2019-11-11 8:40 ` Fwd: " Lee Jones
2019-12-10 8:08 ` Geert Uytterhoeven
2019-10-16 21:06 ` [PATCH v5 2/4] lib: devres: add a helper function for ioremap_uc Tuowen Zhao
[not found] ` <20191017143144.9985421848@mail.kernel.org>
2019-10-17 17:49 ` Tuowen Zhao
2019-10-18 16:47 ` Sasha Levin
2019-12-04 15:51 ` Tuowen Zhao
2019-12-04 19:54 ` Andy Shevchenko
2019-12-04 20:06 ` Tuowen Zhao
2019-12-16 13:06 ` Greg KH
2019-12-16 18:02 ` Tuowen Zhao
2019-11-11 8:41 ` Lee Jones
2019-12-10 8:06 ` Geert Uytterhoeven
2019-12-10 12:50 ` Lee Jones
2019-10-16 21:06 ` [PATCH v5 3/4] mfd: intel-lpss: use devm_ioremap_uc for MMIO Tuowen Zhao
2019-10-22 19:01 ` Roman Gilg
2019-11-11 8:41 ` Lee Jones
2019-12-10 8:11 ` Geert Uytterhoeven
2019-10-16 21:06 ` [PATCH v5 4/4] docs: driver-model: add devm_ioremap_uc Tuowen Zhao
2019-10-23 11:26 ` Luis Chamberlain
2019-11-11 8:41 ` Lee Jones
2019-10-17 7:14 ` [PATCH v5 0/4] Fix MTRR bug for intel-lpss-pci Andy Shevchenko
2019-10-17 7:31 ` Lee Jones
2019-10-17 8:04 ` Andy Shevchenko [this message]
2019-10-17 8:22 ` Lee Jones
2019-10-17 9:52 ` Andy Shevchenko
2019-11-11 8:43 ` [GIT PULL] Immutable branch between MFD, Docs, Sparc and Lib Devres due for the v5.5 merge window Lee Jones
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=20191017080400.GE32742@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=acelan.kao@canonical.com \
--cc=davem@davemloft.net \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=ztuowen@gmail.com \
/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).