From: Rob Herring <robh@kernel.org>
To: jojo_zeng@126.com
Cc: frowand.list@gmail.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] of/device.c: fix the wrong comments
Date: Wed, 1 May 2019 19:33:17 -0500 [thread overview]
Message-ID: <20190502003317.GA19775@bogus> (raw)
In-Reply-To: <1556156754-18993-1-git-send-email-jojo_zeng@126.com>
On Thu, Apr 25, 2019 at 09:45:54AM +0800, jojo_zeng@126.com wrote:
> From: Jojo Zeng <jojo_zeng@126.com>
>
> the comments which discribed the input parameters of of_match_device().
> the name is changed, so fix it.
>
> Signed-off-by: Jojo Zeng <jojo_zeng@126.com>
> ---
> drivers/of/device.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied.
Rob
prev parent reply other threads:[~2019-05-02 0:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 1:45 [PATCH] of/device.c: fix the wrong comments jojo_zeng
2019-04-26 19:31 ` Frank Rowand
2019-05-02 0:33 ` 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=20190502003317.GA19775@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=jojo_zeng@126.com \
--cc=linux-kernel@vger.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).