All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Fabien Dessenne <fabien.dessenne@st.com>
Cc: Ohad Ben-Cohen <ohad@wizery.com>,
	linux-remoteproc@vger.kernel.org,
	Loic Pallardy <loic.pallardy@st.com>,
	Arnaud Pouliquen <arnaud.pouliquen@st.com>
Subject: Re: [PATCH] remoteproc: fix kernel-doc comment for parse_fw
Date: Wed, 7 Nov 2018 22:27:14 -0800	[thread overview]
Message-ID: <20181108062714.GZ12063@builder> (raw)
In-Reply-To: <1541585914-27095-1-git-send-email-fabien.dessenne@st.com>

On Wed 07 Nov 02:18 PST 2018, Fabien Dessenne wrote:

> Fix the kernel-doc comment for "parse_fw" and fix a typo.
> 
> Signed-off-by: Fabien Dessenne <fabien.dessenne@st.com>

Thanks Fabien, applied for v4.21

Regards,
Bjorn

> ---
>  include/linux/remoteproc.h | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/include/linux/remoteproc.h b/include/linux/remoteproc.h
> index e3c5d85..3c83d0f 100644
> --- a/include/linux/remoteproc.h
> +++ b/include/linux/remoteproc.h
> @@ -332,9 +332,9 @@ struct firmware;
>   * @stop:	power off the device
>   * @kick:	kick a virtqueue (virtqueue id given as a parameter)
>   * @da_to_va:	optional platform hook to perform address translations
> - * @load_rsc_table:	load resource table from firmware image
> + * @parse_fw:	parse firmware to extract information (e.g. resource table)
>   * @find_loaded_rsc_table: find the loaded resouce table
> - * @load:		load firmeware to memory, where the remote processor
> + * @load:		load firmware to memory, where the remote processor
>   *			expects to find it
>   * @sanity_check:	sanity check the fw image
>   * @get_boot_addr:	get boot address to entry point specified in firmware
> -- 
> 2.7.4
> 

      reply	other threads:[~2018-11-08  6:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-07 10:18 [PATCH] remoteproc: fix kernel-doc comment for parse_fw Fabien Dessenne
2018-11-08  6:27 ` Bjorn Andersson [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=20181108062714.GZ12063@builder \
    --to=bjorn.andersson@linaro.org \
    --cc=arnaud.pouliquen@st.com \
    --cc=fabien.dessenne@st.com \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=loic.pallardy@st.com \
    --cc=ohad@wizery.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.