public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Stephan Gerhold <stephan@gerhold.net>
Subject: Re: [PATCH] mfd: ab8500: Fix ab8500-clk typo
Date: Fri, 17 Jan 2020 13:41:52 +0000	[thread overview]
Message-ID: <20200117134152.GN15507@dell> (raw)
In-Reply-To: <CACRpkdYQjXyFZfwpk8y66R2XTSm5fEMCb-s-WzPt0KegsCptFQ@mail.gmail.com>

On Fri, 17 Jan 2020, Linus Walleij wrote:

> On Mon, Dec 16, 2019 at 4:22 PM Lee Jones <lee.jones@linaro.org> wrote:
> > On Wed, 11 Dec 2019, Linus Walleij wrote:
> >
> > > Commit f4d41ad84433 ("mfd: ab8500: Example using new OF_MFD_CELL MACRO")
> > > has a typo error renaming "ab8500-clk" to "abx500-clk"
> > > with the result att ALSA SoC audio broke as the clock
> > > driver was not probing anymore. Fixed it up.
> > >
> > > Cc: Stephan Gerhold <stephan@gerhold.net>
> > > Fixes: f4d41ad84433 ("mfd: ab8500: Example using new OF_MFD_CELL MACRO")
> > > Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> > > ---
> > >  drivers/mfd/ab8500-core.c | 4 ++--
> > >  1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > Applied, thanks.
> 
> For some reason this patch doesn't appear in mainline or linux-next,
> I guess it fell off the planet somehow :D
> 
> Or do I look in the wrong place?
> 
> Lee, could you look into it?

It was there, just not pushed in a while.

Pushed now, should be in -next tomorrow.

-- 
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

      reply	other threads:[~2020-01-17 13:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-11 11:46 [PATCH] mfd: ab8500: Fix ab8500-clk typo Linus Walleij
2019-12-11 17:18 ` Stephan Gerhold
2019-12-16 15:22 ` Lee Jones
2020-01-17 10:17   ` Linus Walleij
2020-01-17 13:41     ` Lee Jones [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=20200117134152.GN15507@dell \
    --to=lee.jones@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stephan@gerhold.net \
    /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