From: Marc Zyngier <maz@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Saravana Kannan <saravanak@google.com>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Jisheng Zhang <Jisheng.Zhang@synaptics.com>,
Kever Yang <kever.yang@rock-chips.com>,
Android Kernel Team <kernel-team@android.com>,
linux-gpio@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] gpiolib: Bind gpio_device to a driver to enable fw_devlink=on by default
Date: Wed, 20 Jan 2021 15:58:29 +0000 [thread overview]
Message-ID: <2c2950c5bf94e456560704dbfa48ed16@kernel.org> (raw)
In-Reply-To: <YAhQzxaHCffpPSdQ@kroah.com>
On 2021-01-20 15:48, Greg Kroah-Hartman wrote:
> On Wed, Jan 20, 2021 at 03:39:30PM +0000, Marc Zyngier wrote:
>> Anyway, I said what I had to say. If platforms break with this
>> change, I'll expect it to be disabled in 5.12.
>
> I'm thinking we can not change the default and will probably revert
> this
> patch "soon".
I think there is a lot of value in keeping this enabled for a bit,
so that we can work out what breaks, and find solutions that scale
a bit better.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2021-01-20 16:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 1:14 [PATCH v2] gpiolib: Bind gpio_device to a driver to enable fw_devlink=on by default Saravana Kannan
2021-01-16 20:37 ` Andy Shevchenko
2021-01-17 12:02 ` Marc Zyngier
2021-01-18 20:38 ` Saravana Kannan
2021-01-20 15:39 ` Marc Zyngier
2021-01-20 15:48 ` Greg Kroah-Hartman
2021-01-20 15:58 ` Marc Zyngier [this message]
2021-01-20 17:01 ` Greg Kroah-Hartman
2021-01-21 13:00 ` Linus Walleij
2021-01-21 19:43 ` Saravana Kannan
2021-01-22 13:04 ` Linus Walleij
-- strict thread matches above, loose matches on Subject: below --
2021-01-22 19:35 [PATCH v5] " Saravana Kannan
[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
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=2c2950c5bf94e456560704dbfa48ed16@kernel.org \
--to=maz@kernel.org \
--cc=Jisheng.Zhang@synaptics.com \
--cc=bgolaszewski@baylibre.com \
--cc=gregkh@linuxfoundation.org \
--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=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).