From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Mark Brown <broonie@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: linux-next: Tree for Mar 10 (drivers/spi/spi-mpc512x-psc.c:)
Date: Sun, 12 Mar 2023 10:50:06 +1100 [thread overview]
Message-ID: <20230312105006.6c46df35@canb.auug.org.au> (raw)
In-Reply-To: <ed382974-1613-8a60-913c-60cfc27f8ab3@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 854 bytes --]
Hi all,
On Sat, 11 Mar 2023 15:36:10 -0800 Randy Dunlap <rdunlap@infradead.org> wrote:
>
> On 3/9/23 17:48, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20230309:
> >
> > Non-merge commits (relative to Linus' tree): 2087
> > 2412 files changed, 75248 insertions(+), 89600 deletions(-)
> >
> > ----------------------------------------------------------------------------
>
> on ppc32:
>
> drivers/spi/spi-mpc512x-psc.c: In function 'mpc512x_psc_spi_of_probe':
> drivers/spi/spi-mpc512x-psc.c:518:17: error: label 'free_ipg_clock' used but not defined
> 518 | goto free_ipg_clock;
> | ^~~~
>
>
> on allmodconfig.
Caused by commit
9e21720a4958 ("spi: mpc5xxx-psc: use devm_clk_get_enabled() for core clock")
from the spi tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-03-11 23:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 1:48 linux-next: Tree for Mar 10 Stephen Rothwell
2023-03-11 23:36 ` linux-next: Tree for Mar 10 (drivers/spi/spi-mpc512x-psc.c:) Randy Dunlap
2023-03-11 23:50 ` Stephen Rothwell [this message]
2023-03-13 11:45 ` Andy Shevchenko
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=20230312105006.6c46df35@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).