From: Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH 0/2] peci: aspeed: Add AST2600 compatible
Date: Thu, 3 Oct 2019 09:20:10 -0700 [thread overview]
Message-ID: <b219c8e9-4f72-f91c-ba57-96ffab82ff2e@linux.intel.com> (raw)
In-Reply-To: <4af9eb8fa6fd41fc87708fc8afdcc83e@TWMBX02.aspeed.com>
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
next prev parent reply other threads:[~2019-10-03 16:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 6:11 [PATCH 0/2] peci: aspeed: Add AST2600 compatible Chia-Wei, Wang
2019-10-02 6:11 ` [PATCH 1/2] peci: aspeed: Add AST2600 compatible string Chia-Wei, Wang
2019-10-02 6:12 ` [PATCH 2/2] dt-bindings: peci: aspeed: Add AST2600 compatible Chia-Wei, Wang
2019-10-15 19:01 ` Rob Herring
2019-10-02 18:11 ` [PATCH 0/2] " Jae Hyun Yoo
2019-10-02 22:05 ` Joel Stanley
2019-10-02 23:42 ` Jae Hyun Yoo
2019-10-03 2:35 ` ChiaWei Wang
2019-10-03 16:20 ` Jae Hyun Yoo [this message]
2019-10-04 1:34 ` ChiaWei Wang
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=b219c8e9-4f72-f91c-ba57-96ffab82ff2e@linux.intel.com \
--to=jae.hyun.yoo@linux.intel.com \
--cc=linux-aspeed@lists.ozlabs.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).