linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Saravana Kannan <saravanak@google.com>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	Marc Zyngier <maz@kernel.org>,
	Jisheng Zhang <Jisheng.Zhang@synaptics.com>,
	Kever Yang <kever.yang@rock-chips.com>,
	Android Kernel Team <kernel-team@android.com>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5] gpiolib: Bind gpio_device to a driver to enable fw_devlink=on by default
Date: Tue, 26 Jan 2021 09:14:39 +0100	[thread overview]
Message-ID: <YA/Pb08rCg5x1X7z@kroah.com> (raw)
In-Reply-To: <CACRpkdbid_LbxfmJ3cN7R1jupvOxeY10tXR=O79LAqgqg5H4ug@mail.gmail.com>

On Sun, Jan 24, 2021 at 11:48:28PM +0100, Linus Walleij wrote:
> On Sun, Jan 24, 2021 at 3:54 AM Saravana Kannan <saravanak@google.com> wrote:
> 
> >  Considering the "Fixes" is only in driver-core-next, should this go
> > through driver-core?
> 
> I think Bartosz should pick it up as a GPIO fix for the -rc:s
> because it touches code that he is managing.

Ok, that's fine with me, but if not, I can easily take it as well, just
let me know.

thanks,

greg k-h

  reply	other threads:[~2021-01-26 17:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22 19:35 [PATCH v5] gpiolib: Bind gpio_device to a driver to enable fw_devlink=on by default Saravana Kannan
2021-01-23 22:52 ` Linus Walleij
2021-01-24  2:53   ` Saravana Kannan
2021-01-24 22:48     ` Linus Walleij
2021-01-26  8:14       ` Greg Kroah-Hartman [this message]
     [not found] ` <CAHp75VfKiuVd7JO-0nwCuvy7tgPZScOpKX8Q4+oT+JSBR+d=ew@mail.gmail.com>
2021-01-26 18:16   ` [PATCH v2] " Saravana Kannan
2021-01-26 18:32     ` Andy Shevchenko
2021-01-27 14:22 ` [PATCH v5] " Greg Kroah-Hartman
2021-01-27 14:31   ` Bartosz Golaszewski
2021-01-27 15:04     ` Greg Kroah-Hartman
2021-01-30 17:39 ` Dmitry Osipenko
2021-01-31 21:28   ` Saravana Kannan
2021-02-01 16:49     ` Dmitry Osipenko
2021-02-01 20:15       ` Saravana Kannan
2021-02-01 21:15         ` Dmitry Osipenko

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=YA/Pb08rCg5x1X7z@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Jisheng.Zhang@synaptics.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=kernel-team@android.com \
    --cc=kever.yang@rock-chips.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=saravanak@google.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).