From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-gpio@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [rft, PATCH v2 1/1] gpiolib: Get rid of not used of_node member
Date: Fri, 4 Nov 2022 19:20:53 +0200 [thread overview]
Message-ID: <Y2VJ9ZLEitrJsT7c@smile.fi.intel.com> (raw)
In-Reply-To: <CAMRc=McicB36evBh5thWPtnMPuzbfY+4m29i6Mp-1tJSw9OvjQ@mail.gmail.com>
On Fri, Nov 04, 2022 at 04:09:59PM +0100, Bartosz Golaszewski wrote:
> On Thu, Nov 3, 2022 at 7:06 PM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> >
> > All new drivers should use fwnode and / or parent to provide the
> > necessary information to the GPIO library.
...
> This looks good to me.
Thank you!
> I'm thinking about just applying it and giving
> it a spin in next right away.
I would like to split it, one patch, btw, had been already sent separately.
So, if you are going for the Linux Next, I would like to ask for rebasing
later on.
Also note, it requires patches that are in Linus' W. and mine trees.
It will fail if you apply without those to be proceeded first.
> Linus: any objections?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-11-04 17:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 18:06 [rft, PATCH v2 1/1] gpiolib: Get rid of not used of_node member Andy Shevchenko
2022-11-04 15:09 ` Bartosz Golaszewski
2022-11-04 17:20 ` Andy Shevchenko [this message]
2022-11-08 10:47 ` Linus Walleij
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=Y2VJ9ZLEitrJsT7c@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=dmitry.torokhov@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
/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).