From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wang, Haiyue Date: Fri, 23 Feb 2018 09:44:58 +0800 Subject: [PATCH] MAINTAINERS: Update ASPEED entry with details In-Reply-To: <1519344667.1024159.1280347184.36AD3FEC@webmail.messagingengine.com> References: <20180222050324.21531-1-joel@jms.id.au> <1519288786.101739.1279390200.1CD3EC51@webmail.messagingengine.com> <23b668f1-ab4b-7ef3-ba1e-f252fbba4d1b@linux.intel.com> <1519344667.1024159.1280347184.36AD3FEC@webmail.messagingengine.com> Message-ID: List-Id: To: linux-aspeed@lists.ozlabs.org MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable On 2018-02-23 08:11, Andrew Jeffery wrote: > Hi Haiyue, > > On Thu, 22 Feb 2018, at 19:20, Wang, Haiyue wrote: >> 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=C2=A0 has been remove= d, >> 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/ >> > There are some comments against the v1 that you linked to above, is there= a v2 on the lists? A long holiday back, will send v2 patch soon. > Separately it's better to ping us by replying to the patch itself and put= ting us in To/Cc, that way we keep discussions focused on the patch at hand= here. Got it. Thanks for your reply. > > Cheers, > > Andrew