From: Rob Herring <robh@kernel.org>
To: qiwuchen55@gmail.com
Cc: devicetree@vger.kernel.org, chenqiwu <chenqiwu@xiaomi.com>,
robh+dt@kernel.org, frowand.list@gmail.com
Subject: Re: [PATCH] drivers/of: keep description of function consistent with function name
Date: Tue, 19 May 2020 12:24:26 -0600 [thread overview]
Message-ID: <20200519182426.GA418146@bogus> (raw)
In-Reply-To: <1589209497-13945-1-git-send-email-qiwuchen55@gmail.com>
On Mon, 11 May 2020 23:04:57 +0800, wrote:
> From: chenqiwu <chenqiwu@xiaomi.com>
>
> Currently, there are some descriptions of function not
> consistent with function name, fixing them will make
> the code more readable.
>
> Signed-off-by: chenqiwu <chenqiwu@xiaomi.com>
> ---
> drivers/of/fdt.c | 2 +-
> drivers/of/of_reserved_mem.c | 10 +++++-----
> 2 files changed, 6 insertions(+), 6 deletions(-)
>
Applied, thanks!
prev parent reply other threads:[~2020-05-19 18:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 15:04 [PATCH] drivers/of: keep description of function consistent with function name qiwuchen55
2020-05-19 18:24 ` Rob Herring [this message]
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=20200519182426.GA418146@bogus \
--to=robh@kernel.org \
--cc=chenqiwu@xiaomi.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=qiwuchen55@gmail.com \
--cc=robh+dt@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).