[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <23b668f1-ab4b-7ef3-ba1e-f252fbba4d1b@linux.intel.com>
Date: Thu, 22 Feb 2018 16:50:17 +0800
From: "Wang, Haiyue" <haiyue.wang@...ux.intel.com>
To: Andrew Jeffery <andrew@...id.au>, Joel Stanley <joel@....id.au>,
Arnd Bergmann <arnd@...db.de>, Olof Johansson <olof@...om.net>
Cc: linux-arm-kernel@...ts.infradead.org,
linux-aspeed@...ts.ozlabs.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Update ASPEED entry with details
Dear Andrew & Joel,
Since you are ASPEED BMC experts, any time and interest in eSPI code
review ? I've sent
it before, but no more response. Intel recommends eSPI bus than LPC as I
know. I just kept
the minimal eSPI code which is approved to work well in our real server
boards for two more
years. Other part of eSPI driver from ASPEED's SDK has been removed,
because ePSI is a new
thing, we only use a small feature set like booting host.
We Intel submit this eSPI patch for openbmc upstreaming, hope for your
response. :-)
https://patchwork.kernel.org/patch/10166577/
On 2018-02-22 16:39, Andrew Jeffery wrote:
>
> On Thu, 22 Feb 2018, at 15:33, Joel Stanley wrote:
>> I am interested in all ASPEED drivers, and the previous match wasn't
>> grabbing files in nested directories. Use N instead.
>>
>> Add the arm kernel mailing list so that patches get reviewed there, and
>> the linux-aspeed list which exists only so I can use patchwork to track
>> patches.
>>
>> Add Andrew as a reviewer, because he is involved in reviewing ASPEED
>> stuff.
>>
>> Signed-off-by: Joel Stanley <joel@....id.au>
> Acked-by: Andrew Jeffery <andrew@...id.au>
Powered by blists - more mailing lists