From: "Andrew Jeffery" <andrew@aj.id.au>
To: manikandan-e <manikandan.hcl.ers.epl@gmail.com>
Cc: "Joel Stanley" <joel@jms.id.au>, "Sai Dasari" <sdasari@fb.com>,
"Vijay Khemka" <vijaykhemka@fb.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-aspeed@lists.ozlabs.org, manikandan.e@hcl.com
Subject: Re: [PATCH v4] ARM: dts: aspeed: Adding Facebook Yosemite V2 BMC
Date: Thu, 28 Nov 2019 09:05:21 +1030 [thread overview]
Message-ID: <ba027dc2-613c-40c6-bb5e-1d320e51b191@www.fastmail.com> (raw)
In-Reply-To: <20191127132340.GA22672@cnn>
On Wed, 27 Nov 2019, at 23:53, manikandan-e wrote:
> The Yosemite V2 is a facebook multi-node server
> platform that host four OCP server. The BMC
> in the Yosemite V2 platorm based on AST2500 SoC.
>
> This patch adds linux device tree entry related to
> Yosemite V2 specific devices connected to BMC SoC.
>
> Signed-off-by: manikandan-e <manikandan.hcl.ers.epl@gmail.com>
If people have reviewed previous versions of your patches and sent
Reviewed-by/Acked-by/Tested-by tags, please make sure to include
them on future versions of the patches _unless_ there has been
significant change that might invalidate the tag. In that case, also
provide a short description as to why you dropped the tags. You can
add free-form information below the `---` and it will not be included
in the commit for the patch.
Cheers,
Andrew
next prev parent reply other threads:[~2019-11-27 22:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 13:23 [PATCH v4] ARM: dts: aspeed: Adding Facebook Yosemite V2 BMC manikandan-e
2019-11-27 22:35 ` Andrew Jeffery [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-27 6:07 manikandan-e
2019-11-27 13:14 ` Vijay Khemka
2019-11-28 0:45 ` Joel Stanley
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=ba027dc2-613c-40c6-bb5e-1d320e51b191@www.fastmail.com \
--to=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manikandan.e@hcl.com \
--cc=manikandan.hcl.ers.epl@gmail.com \
--cc=sdasari@fb.com \
--cc=vijaykhemka@fb.com \
/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).