[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191120140233.GB2935300@kroah.com>
Date: Wed, 20 Nov 2019 15:02:33 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: patrick.rudolph@...ements.com
Cc: linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
Alexios Zavras <alexios.zavras@...el.com>,
Allison Randal <allison@...utok.net>,
Samuel Holland <samuel@...lland.org>,
Julius Werner <jwerner@...omium.org>,
Stephen Boyd <swboyd@...omium.org>
Subject: Re: [PATCH 0/2] firmware: google: Expose coreboot tables and CBMEM
On Wed, Nov 20, 2019 at 02:39:45PM +0100, patrick.rudolph@...ements.com wrote:
> From: Patrick Rudolph <patrick.rudolph@...ements.com>
>
> As user land tools currently use /dev/mem to access coreboot tables and
> CBMEM, provide a better way by using read-only sysfs attributes.
>
> Unconditionally expose all tables and buffers making future changes in
> coreboot possible without modifying a kernel driver.
>
> Changes in v2:
> - Add ABI documentation
> - Add 0x prefix on hex values
> - Remove wrong ioremap hint as found by CI
I think you forgot to put "v2" in the [PATCH] area of the subject lines
:(
thanks,
greg k-h
Powered by blists - more mailing lists