linux-kernel - Re: [PATCH] MAINTAINERS: Update ASPEED entry with details

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 23 Feb 2018 09:44:58 +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



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  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/
>>
> 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 putting us in To/Cc, that way we keep discussions focused on the patch at hand here.
Got it. Thanks for your reply.
>
> Cheers,
>
> Andrew