From: "Wang, Haiyue" <haiyue.wang@linux.intel.com>
To: Joel Stanley <joel@jms.id.au>
Cc: Andrew Jeffery <andrew@aj.id.au>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH dts/arm/aspeed-g5 v1] ARM: dts: aspeed-g5: Add IPMI KCS node
Date: Wed, 7 Mar 2018 12:41:35 +0800 [thread overview]
Message-ID: <ff3a6480-5df7-e3da-b086-4bdcbb63708a@linux.intel.com> (raw)
In-Reply-To: <CACPK8XevaaJSn2eZUt3dfAK+eOJ-hifnMqMme120jCRszpth1A@mail.gmail.com>
On 2018-03-07 11:56, Joel Stanley wrote:
>> And the patch is generated by rebasing on:
>> https://git.kernel.org/pub/scm/linux/kernel/git/joel/aspeed.git
>> Please help to review.
> Thanks for the patch. I suggest you submit this patch for inclusion in
> the upstream kernel. To do this, send it to:
> Joel Stanley<joel@jms.id.au>
> Andrew Jeffery<andrew@aj.id.au>
> linux-arm-kernel@lists.infradead.org
> linux-aspeed@lists.ozlabs.org
> linux-kernel@vger.kernel.org
Got it.
> And I will consider it for merging.
>
> From there I can backport it into the dev-4.13 tree.
>
> Cheers,
>
> Joel
>
next prev parent reply other threads:[~2018-03-07 4:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-04 5:03 [PATCH dts/arm/aspeed-g5 v1] ARM: dts: aspeed-g5: Add IPMI KCS node Haiyue Wang
2018-03-07 3:56 ` Joel Stanley
2018-03-07 3:56 ` Joel Stanley
2018-03-07 4:41 ` Wang, Haiyue [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-07 5:04 Haiyue Wang
2018-03-07 5:04 ` Haiyue Wang
2018-03-07 5:04 ` Haiyue Wang
2018-03-16 0:47 ` Wang, Haiyue
2018-03-16 0:47 ` Wang, Haiyue
2018-03-16 0:47 ` Wang, Haiyue
2018-05-25 4:34 ` Joel Stanley
2018-05-25 4:34 ` Joel Stanley
2018-05-25 4:34 ` Joel Stanley
2018-05-25 11:33 ` Wang, Haiyue
2018-05-25 11:33 ` Wang, Haiyue
2018-05-25 11:33 ` Wang, Haiyue
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=ff3a6480-5df7-e3da-b086-4bdcbb63708a@linux.intel.com \
--to=haiyue.wang@linux.intel.com \
--cc=andrew@aj.id.au \
--cc=joel@jms.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.