public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux•intel.com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Randy Dunlap <rdunlap@infradead•org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Mark Brown <broonie@kernel•org>
Subject: Re: linux-next: Tree for Mar 10 (drivers/spi/spi-mpc512x-psc.c:)
Date: Mon, 13 Mar 2023 13:45:32 +0200	[thread overview]
Message-ID: <ZA8M3NZbMxi80z7O@smile.fi.intel.com> (raw)
In-Reply-To: <20230312105006.6c46df35@canb.auug.org.au>

On Sun, Mar 12, 2023 at 10:50:06AM +1100, Stephen Rothwell wrote:
> On Sat, 11 Mar 2023 15:36:10 -0800 Randy Dunlap <rdunlap@infradead•org> wrote:
> > On 3/9/23 17:48, Stephen Rothwell wrote:

...

> > 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.

It's fixed already in the SPI tree.

-- 
With Best Regards,
Andy Shevchenko



      reply	other threads:[~2023-03-13 11:48 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
2023-03-13 11:45     ` Andy Shevchenko [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=ZA8M3NZbMxi80z7O@smile.fi.intel.com \
    --to=andriy.shevchenko@linux$(echo .)intel.com \
    --cc=broonie@kernel$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=rdunlap@infradead$(echo .)org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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