public inbox for linux-remoteproc@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-remoteproc@kernel.org
To: Souptick Joarder <jrdr.linux@gmail.com>
Cc: linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH] remoteproc/mediatek: Fix kernel test robot warning
Date: Sat, 28 Nov 2020 03:40:06 +0000	[thread overview]
Message-ID: <160653480638.19310.11778877879471121427.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1606513855-21130-1-git-send-email-jrdr.linux@gmail.com>

Hello:

This patch was applied to andersson/remoteproc.git (refs/heads/for-next):

On Sat, 28 Nov 2020 03:20:55 +0530 you wrote:
> Kernel test robot throws below warning ->
> 
> >> drivers/remoteproc/mtk_scp.c:755:37: warning: unused variable
> >> 'mt8183_of_data' [-Wunused-const-variable]
>    static const struct mtk_scp_of_data mt8183_of_data = {
>                                        ^
> >> drivers/remoteproc/mtk_scp.c:765:37: warning: unused variable
> >> 'mt8192_of_data' [-Wunused-const-variable]
>    static const struct mtk_scp_of_data mt8192_of_data = {
>                                        ^
> As suggested by Bjorn, there's no harm in just dropping the
> of_match_ptr() wrapping of mtk_scp_of_match in the definition of
> mtk_scp_driver and we avoid this whole problem.
> 
> [...]

Here is the summary with links:
  - remoteproc/mediatek: Fix kernel test robot warning
    https://git.kernel.org/andersson/remoteproc/c/8c09e5fdf31b

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2020-11-28  3:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-27 21:50 [PATCH] remoteproc/mediatek: Fix kernel test robot warning Souptick Joarder
2020-11-28  3:40 ` 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=160653480638.19310.11778877879471121427.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-remoteproc@kernel.org \
    --cc=jrdr.linux@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox