linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <Conor.Dooley@microchip.com>
To: <sfr@canb.auug.org.au>, <jaswinder.singh@linaro.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the mailbox tree
Date: Mon, 21 Jun 2021 14:11:06 +0000	[thread overview]
Message-ID: <1b6c7de7-3e0d-1812-0a1f-4e7106ad83c3@microchip.com> (raw)
In-Reply-To: <20210621155752.28d0524a@canb.auug.org.au>

On 21/06/2021 06:57, Stephen Rothwell wrote:
> Hi all,
>
> After merging the mailbox tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> In file included from drivers/mailbox/mailbox-mpfs.c:19:
> include/soc/microchip/mpfs.h:43:12: warning: 'mpfs_blocking_transaction' defined but not used [-Wunused-function]
>     43 | static int mpfs_blocking_transaction(struct mpfs_sys_controller *mpfs_client, void *msg,
>        |            ^~~~~~~~~~~~~~~~~~~~~~~~~
>
> Introduced by commit
>
>    de5473936808 ("mbox: add polarfire soc system controller mailbox")
>
> -- Cheers, Stephen Rothwell

Hi,
That function is defined for services using the mailbox, and since 
currently none exist it is redundant. I will move it to another patch 
series that adds the services and resubmit this series.

Thanks,
Conor.



      reply	other threads:[~2021-06-21 14:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-21  5:57 linux-next: build warning after merge of the mailbox tree Stephen Rothwell
2021-06-21 14:11 ` Conor.Dooley [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=1b6c7de7-3e0d-1812-0a1f-4e7106ad83c3@microchip.com \
    --to=conor.dooley@microchip.com \
    --cc=jaswinder.singh@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).