public inbox for linux-remoteproc@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-remoteproc@kernel.org
To: Alexandre Courbot <acourbot@chromium.org>
Cc: linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH] remoteproc/mtk_scp: surround DT device IDs with CONFIG_OF
Date: Wed, 18 Nov 2020 14:30:06 +0000	[thread overview]
Message-ID: <160570980688.9988.13065730747493473016.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201102074007.299222-1-acourbot@chromium.org>

Hello:

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

On Mon,  2 Nov 2020 16:40:07 +0900 you wrote:
> Now that this driver can be compiled with COMPILE_TEST, we have no
> guarantee that CONFIG_OF will also be defined. When that happens, a
> warning about mtk_scp_of_match being defined but unused will be reported
> so make sure this variable is only defined if of_match_ptr() actually
> uses it.
> 
> Fixes: cbd2dca74926c0e4610c40923cc786b732c9e8ef remoteproc: scp: add COMPILE_TEST dependency
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Alexandre Courbot <acourbot@chromium.org>
> 
> [...]

Here is the summary with links:
  - remoteproc/mtk_scp: surround DT device IDs with CONFIG_OF
    https://git.kernel.org/andersson/remoteproc/c/b8ba90450331

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



      parent reply	other threads:[~2020-11-18 14:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02  7:40 [PATCH] remoteproc/mtk_scp: surround DT device IDs with CONFIG_OF Alexandre Courbot
2020-11-04 19:05 ` Mathieu Poirier
2020-11-05  4:55   ` Bjorn Andersson
2020-11-18 14:30 ` 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=160570980688.9988.13065730747493473016.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-remoteproc@kernel.org \
    --cc=acourbot@chromium.org \
    --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