From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v1 2/2] x86: zImage: Propagate acpi_rsdp_addr to kernel via boot parameters
Date: Wed, 22 Aug 2018 13:23:19 +0300 [thread overview]
Message-ID: <ff120ae68548c44de416cda98a7d7bfd93f8489d.camel@linux.intel.com> (raw)
In-Reply-To: <CAEUhbmWPADjgUBaGKty2ig7vJdJ8ScijiHdF3hG=f8OybZRukA@mail.gmail.com>
On Wed, 2018-08-22 at 17:05 +0800, Bin Meng wrote:
> Hi Andy,
>
> On Mon, Jun 18, 2018 at 9:52 PM, Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> > On Mon, 2018-06-18 at 16:27 +0300, Andy Shevchenko wrote:
> > > On Mon, 2018-06-18 at 21:03 +0800, Bin Meng wrote:
> > > > On Mon, Jun 18, 2018 at 5:22 PM, Andy Shevchenko
> > > > <andriy.shevchenko@linux.intel.com> wrote:
> > > > >
> >
> >
> > > > I did not find the discussion. Do we need revert the changes in
> > > > U-
> > > > Boot?
> > >
> > > https://patchwork.kernel.org/patch/10098529/
> > >
> > > It seems it has been dropped b/c v2 were sent and actually v3 was
> > > anticipated, but never appear.
> >
> > Hmm... I'm wrong there is v3 and stated as applied.
> >
> >
https://www.mail-archive.com/linux-kernel at vger.kernel.org/msg1559618.htm
> > l
> >
> > Though in next-20180112 it was appeared last time.
> >
> >
> >
> > This one seems explains what is the issue with this field
> >
> >
https://www.mail-archive.com/xen-devel at lists.xenproject.org/msg04706.htm
> > l
> >
> > >
> > > Also I didn't notice any blessing from hpa about protocol
> > > extension.
>
> Sorry to bring this again. Looks as of today the addition to the
> acpi_rsdp_addr member is still not merged mainstream kernel. Do you
> think we need revert this in U-Boot, or keep it there but may cause
> some confusion?
Hmm... I guess I answered to your previous message.
Anyway, I agree for the revert until we will have a clear picture with
upstream.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2018-08-22 10:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 17:40 [U-Boot] [PATCH v1 1/2] x86: zImage: Move subarch assignment out of cmd_line check Andy Shevchenko
2018-01-10 17:40 ` [U-Boot] [PATCH v1 2/2] x86: zImage: Propagate acpi_rsdp_addr to kernel via boot parameters Andy Shevchenko
2018-01-12 9:00 ` Bin Meng
2018-01-12 13:01 ` Andy Shevchenko
2018-01-15 2:33 ` Bin Meng
2018-01-30 12:50 ` Bin Meng
2018-06-16 23:22 ` Bin Meng
2018-06-18 9:22 ` Andy Shevchenko
2018-06-18 13:03 ` Bin Meng
2018-06-18 13:27 ` Andy Shevchenko
2018-06-18 13:52 ` Andy Shevchenko
2018-08-22 9:05 ` Bin Meng
2018-08-22 10:23 ` Andy Shevchenko [this message]
2018-01-12 9:00 ` [U-Boot] [PATCH v1 1/2] x86: zImage: Move subarch assignment out of cmd_line check Bin Meng
2018-01-15 2:33 ` Bin Meng
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=ff120ae68548c44de416cda98a7d7bfd93f8489d.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=u-boot@lists.denx.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