From: patchwork-bot+linux-remoteproc@kernel.org
To: Dong Aisheng <aisheng.dong@nxp.com>
Cc: linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH 1/2] remoteproc: fix an typo in fw_elf_get_class code comments
Date: Wed, 04 Aug 2021 19:31:49 +0000 [thread overview]
Message-ID: <162810550950.17752.3513741508941507522.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210706142156.952794-1-aisheng.dong@nxp.com>
Hello:
This series was applied to andersson/remoteproc.git (refs/heads/for-next):
On Tue, 6 Jul 2021 22:21:55 +0800 you wrote:
> Drop 'and' which looks like unnecessary.
>
> Fixes: 73516a33588c ("remoteproc: Add elf helpers to access elf64 and elf32 fields")
> Signed-off-by: Dong Aisheng <aisheng.dong@nxp.com>
> ---
> drivers/remoteproc/remoteproc_elf_helpers.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Here is the summary with links:
- [1/2] remoteproc: fix an typo in fw_elf_get_class code comments
https://git.kernel.org/andersson/remoteproc/c/c080128b6f05
- [2/2] remoteproc: fix kernel doc for struct rproc_ops
https://git.kernel.org/andersson/remoteproc/c/147b589c5f44
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-08-04 19:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-06 14:21 [PATCH 1/2] remoteproc: fix an typo in fw_elf_get_class code comments Dong Aisheng
2021-07-06 14:21 ` Dong Aisheng
2021-07-06 14:21 ` [PATCH 2/2] remoteproc: fix kernel doc for struct rproc_ops Dong Aisheng
2021-07-06 14:21 ` Dong Aisheng
2021-07-12 17:41 ` Mathieu Poirier
2021-07-12 17:41 ` Mathieu Poirier
2021-07-12 17:29 ` [PATCH 1/2] remoteproc: fix an typo in fw_elf_get_class code comments Mathieu Poirier
2021-07-12 17:29 ` Mathieu Poirier
2021-08-04 19:31 ` patchwork-bot+linux-remoteproc [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=162810550950.17752.3513741508941507522.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-remoteproc@kernel.org \
--cc=aisheng.dong@nxp.com \
--cc=linux-remoteproc@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 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.