devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Jiang Jian <jiangjian@cdjrlc.com>
Cc: frowand.list@gmail.com, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] of: device - Remove duplicate 'of' in two places.
Date: Mon, 27 Jun 2022 11:38:25 -0600	[thread overview]
Message-ID: <20220627173825.GA2637590-robh@kernel.org> (raw)
In-Reply-To: <20220621154222.13714-1-jiangjian@cdjrlc.com>

On Tue, Jun 21, 2022 at 11:42:22PM +0800, Jiang Jian wrote:
> file: ./drivers/of/device.c
> line: 22
>  * @matches: array of of device match structures to search in
> changed to
>  * @matches: array of device match structures to search in
> 
> Signed-off-by: Jiang Jian <jiangjian@cdjrlc.com>
> ---
>  drivers/of/device.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/of/device.c b/drivers/of/device.c
> index 874f031442dc..1582388156a9 100644
> --- a/drivers/of/device.c
> +++ b/drivers/of/device.c
> @@ -19,7 +19,7 @@
>  
>  /**
>   * of_match_device - Tell if a struct device matches an of_device_id list
> - * @matches: array of of device match structures to search in
> + * @matches: array of device match structures to search in

Maybe that was supposed to be 'of OF device match'? 

But really, something like 'NULL terminated array of struct of_device_id 
entries to search' would be better.

>   * @dev: the of device structure to match against

Like 'of' here.

>   *
>   * Used by a driver to check whether an platform_device present in the
> -- 
> 2.17.1
> 
> 

      reply	other threads:[~2022-06-27 17:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-21 15:42 [PATCH] of: device - Remove duplicate 'of' in two places Jiang Jian
2022-06-27 17:38 ` 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=20220627173825.GA2637590-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=jiangjian@cdjrlc.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).