[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ad79c20427ea4aa28c826d32e96b82e8@TWMBX02.aspeed.com>
Date: Fri, 4 Oct 2019 01:34:43 +0000
From: ChiaWei Wang <chiawei_wang@...eedtech.com>
To: Jae Hyun Yoo <jae.hyun.yoo@...ux.intel.com>,
Joel Stanley <joel@....id.au>
CC: Jason M Biils <jason.m.bills@...ux.intel.com>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Andrew Jeffery <andrew@...id.au>,
linux-aspeed <linux-aspeed@...ts.ozlabs.org>,
"OpenBMC Maillist" <openbmc@...ts.ozlabs.org>,
devicetree <devicetree@...r.kernel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Ryan Chen <ryan_chen@...eedtech.com>
Subject: RE: [PATCH 0/2] peci: aspeed: Add AST2600 compatible
Sure. We will re-submit the patches with the revision suggested.
Thanks.
Regards,
Chiawei
************* Email Confidentiality Notice ********************
DISCLAIMER:
This message (and any attachments) may contain legally privileged and/or other confidential information. If you have received it in error, please notify the sender by reply e-mail and immediately delete the e-mail and any attachments without copying or disclosing the contents. Thank you.
-----Original Message-----
From: Jae Hyun Yoo [mailto:jae.hyun.yoo@...ux.intel.com]
Sent: Friday, October 4, 2019 12:20 AM
To: ChiaWei Wang <chiawei_wang@...eedtech.com>; Joel Stanley <joel@....id.au>
Cc: Jason M Biils <jason.m.bills@...ux.intel.com>; Rob Herring <robh+dt@...nel.org>; Mark Rutland <mark.rutland@....com>; Andrew Jeffery <andrew@...id.au>; linux-aspeed <linux-aspeed@...ts.ozlabs.org>; OpenBMC Maillist <openbmc@...ts.ozlabs.org>; devicetree <devicetree@...r.kernel.org>; Linux ARM <linux-arm-kernel@...ts.infradead.org>; Linux Kernel Mailing List <linux-kernel@...r.kernel.org>; Ryan Chen <ryan_chen@...eedtech.com>
Subject: Re: [PATCH 0/2] peci: aspeed: Add AST2600 compatible
On 10/2/2019 7:35 PM, ChiaWei Wang wrote:
> Hi Jae Hyun,
>
> Thanks for the feedback.
> For now should I use GitHub pull-request to submit the patches of PECI-related change to OpenBMC dev-5.3 tree only?
You could submit this patch series to OpenBMC mailing list with [PATCH linux dev-5.3] prefix.
Thanks,
Jae
Powered by blists - more mailing lists