From: haiyue.wang@linux.intel.com (Wang, Haiyue)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MAINTAINERS: Update ASPEED entry with details
Date: Fri, 23 Feb 2018 09:44:58 +0800 [thread overview]
Message-ID: <d67a8a8d-4b3d-403c-e62d-bc0939e8d08f@linux.intel.com> (raw)
In-Reply-To: <1519344667.1024159.1280347184.36AD3FEC@webmail.messagingengine.com>
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
next prev parent reply other threads:[~2018-02-23 1:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 5:03 [PATCH] MAINTAINERS: Update ASPEED entry with details Joel Stanley
2018-02-22 8:39 ` Andrew Jeffery
2018-02-22 8:50 ` Wang, Haiyue
2018-02-23 0:11 ` Andrew Jeffery
2018-02-23 1:44 ` Wang, Haiyue [this message]
2018-04-11 4:06 ` Joel Stanley
2018-04-11 8:51 ` Arnd Bergmann
2018-04-11 9:24 ` Joel Stanley
2018-04-11 12:05 ` Arnd Bergmann
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=d67a8a8d-4b3d-403c-e62d-bc0939e8d08f@linux.intel.com \
--to=haiyue.wang@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).