From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Walleij <linus.walleij@linaro.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Scott Wood <oss@buserror.net>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Bartosz Golaszewski <brgl@bgdev.pl>
Subject: Re: [PATCH v1 1/1] powerpc/83xx/mpc8349emitx: Get rid of of_node assignment
Date: Thu, 21 Apr 2022 08:42:30 +1000 [thread overview]
Message-ID: <87fsm7fkbt.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <CACRpkdbqfNiWQG6ayqMXACby4xkW0pY6JhdYE-x+pWkSxJU5TQ@mail.gmail.com>
Linus Walleij <linus.walleij@linaro.org> writes:
> On Wed, Apr 6, 2022 at 3:02 PM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
>> On Mon, Mar 28, 2022 at 03:16:08PM +0200, Linus Walleij wrote:
>> > On Wed, Mar 23, 2022 at 6:43 PM Andy Shevchenko
>> > <andriy.shevchenko@linux.intel.com> wrote:
>> >
>> > > Let GPIO library to assign of_node from the parent device.
>> > > This allows to move GPIO library and drivers to use fwnode
>> > > APIs instead of being stuck with OF-only interfaces.
>> > >
>> > > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>> >
>> > That's a nice patch.
>> > Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
>>
>> Thanks!
>>
>> Can we have this applied now?
>
> I think Michael Ellerman could help with this?
>
> Michael?
Yep, I'll pick it up when I start putting things into next.
That's usually the week after rc2, but I had a break for Easter.
cheers
next prev parent reply other threads:[~2022-04-20 22:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 17:43 [PATCH v1 1/1] powerpc/83xx/mpc8349emitx: Get rid of of_node assignment Andy Shevchenko
2022-03-28 13:16 ` Linus Walleij
2022-04-06 13:01 ` Andy Shevchenko
2022-04-19 21:38 ` Linus Walleij
2022-04-20 22:42 ` Michael Ellerman [this message]
2022-05-04 13:45 ` Andy Shevchenko
2022-05-05 11:04 ` Michael Ellerman
2022-05-05 11:23 ` Andy Shevchenko
2022-04-06 20:13 ` Scott Wood
2022-05-15 10:12 ` Michael Ellerman
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=87fsm7fkbt.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=andriy.shevchenko@linux.intel.com \
--cc=benh@kernel.crashing.org \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=oss@buserror.net \
--cc=paulus@samba.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