From: Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"trivial@kernel.org" <trivial@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] dt-bindings: arm: fix the document ID for SCMI protocol documentation
Date: Thu, 23 May 2019 17:24:56 +0000 [thread overview]
Message-ID: <877eah84nr.fsf@epam.com> (raw)
In-Reply-To: <20190523170938.GC4224@e107155-lin>
Hi,
Sudeep Holla writes:
> On Thu, May 23, 2019 at 11:23:35AM +0000, Volodymyr Babchuk wrote:
>> From: Volodymyr Babchuk <volodymyr_babchuk@epam.com
I accidentally deleted ending ">" symbol in the line above, so "git
send-email" decided to move that line from headers to the message body.
>> arm,scmi.txt used the wrong document identifier. "ARM DUI 0922B" is
>> the "ARM Compute Subsystem SCP, Message Interface Protocols". What we
>> need is the ARM DEN 0056A - "ARM System Control and Management
>> Interface Platform Design Document".
>>
>
> Indeed, it's most stupid copy-paste mistake. Thanks for fixing this.
> Applied now.
It happens all the time. I also did stupid mistake in my patch file. It
is described above. Could you please ensure that this line will be not
in the resulting commit message? Thank you.
--
Best regards,Volodymyr Babchuk
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-05-23 17:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 11:23 [PATCH] dt-bindings: arm: fix the document ID for SCMI protocol documentation Volodymyr Babchuk
2019-05-23 17:09 ` Sudeep Holla
2019-05-23 17:24 ` Volodymyr Babchuk [this message]
2019-05-24 10:54 ` Sudeep Holla
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=877eah84nr.fsf@epam.com \
--to=volodymyr_babchuk@epam.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=trivial@kernel.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).