From: Rob Herring <robh@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
a.fatoum@pengutronix.de, Saravana Kannan <saravanak@google.com>,
Tudor Ambarus <Tudor.Ambarus@microchip.com>,
Stephen Boyd <sboyd@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
linux-clk <linux-clk@vger.kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
mirq-linux@rere.qmqm.pl,
Ludovic Desroches <Ludovic.Desroches@microchip.com>,
Codrin.Ciubotariu@microchip.com,
Claudiu Beznea <Claudiu.Beznea@microchip.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] clk: at91: Fix the declaration of the clocks
Date: Wed, 10 Feb 2021 10:22:26 -0600 [thread overview]
Message-ID: <20210210162226.GA2246688@robh.at.kernel.org> (raw)
In-Reply-To: <YCOgnm2VkSinTYIk@kroah.com>
On Wed, Feb 10, 2021 at 10:00:14AM +0100, Greg Kroah-Hartman wrote:
> On Wed, Feb 10, 2021 at 09:51:14AM +0100, Geert Uytterhoeven wrote:
> > Hi Saravana,
> >
> > On Wed, Feb 10, 2021 at 1:57 AM Saravana Kannan <saravanak@google.com> wrote:
> > > On Tue, Feb 9, 2021 at 4:54 PM Stephen Boyd <sboyd@kernel.org> wrote:
> > > > Quoting Tudor.Ambarus@microchip.com (2021-02-08 01:49:45)
> > > > > Do you plan to take this patch for v5.12?
> > > > > If fw_devlink will remain set to ON for v5.12, some of our boards will
> > > > > no longer boot without this patch.
> > > >
> > > > Is fw_devlink defaulted to on for v5.12?
> > >
> > > Yes.
> >
> > Have all issues been identified and understood?
> > Have all issues been fixed, reviewed, and committed?
> > Have all fixes entered linux-next?
> > Have all fixes been migrated from submaintainers to maintainers?
This can never be true for these types of per platform issues. There are
folks that test linux-next Then there are ones that test rc1. And
(unfortunately) so-on ending at testing only LTS releases.
> > We're already at v5.11-rc7.
> > Yes, we can get fixes into v5.12-rc7. Or v5.12-rc9...
>
> Yeah, I'm leaning toward not making it the default for 5.12-rc1 because
> not everything seems to be working, let's see how the rest of the week
> goes...
I think there's some value waiting until after rc1 to turn off if just
to find a few more issues.
Rob
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
a.fatoum@pengutronix.de, Saravana Kannan <saravanak@google.com>,
Tudor Ambarus <Tudor.Ambarus@microchip.com>,
Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
LKML <linux-kernel@vger.kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
mirq-linux@rere.qmqm.pl,
Ludovic Desroches <Ludovic.Desroches@microchip.com>,
Codrin.Ciubotariu@microchip.com,
Claudiu Beznea <Claudiu.Beznea@microchip.com>,
linux-clk <linux-clk@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] clk: at91: Fix the declaration of the clocks
Date: Wed, 10 Feb 2021 10:22:26 -0600 [thread overview]
Message-ID: <20210210162226.GA2246688@robh.at.kernel.org> (raw)
In-Reply-To: <YCOgnm2VkSinTYIk@kroah.com>
On Wed, Feb 10, 2021 at 10:00:14AM +0100, Greg Kroah-Hartman wrote:
> On Wed, Feb 10, 2021 at 09:51:14AM +0100, Geert Uytterhoeven wrote:
> > Hi Saravana,
> >
> > On Wed, Feb 10, 2021 at 1:57 AM Saravana Kannan <saravanak@google.com> wrote:
> > > On Tue, Feb 9, 2021 at 4:54 PM Stephen Boyd <sboyd@kernel.org> wrote:
> > > > Quoting Tudor.Ambarus@microchip.com (2021-02-08 01:49:45)
> > > > > Do you plan to take this patch for v5.12?
> > > > > If fw_devlink will remain set to ON for v5.12, some of our boards will
> > > > > no longer boot without this patch.
> > > >
> > > > Is fw_devlink defaulted to on for v5.12?
> > >
> > > Yes.
> >
> > Have all issues been identified and understood?
> > Have all issues been fixed, reviewed, and committed?
> > Have all fixes entered linux-next?
> > Have all fixes been migrated from submaintainers to maintainers?
This can never be true for these types of per platform issues. There are
folks that test linux-next Then there are ones that test rc1. And
(unfortunately) so-on ending at testing only LTS releases.
> > We're already at v5.11-rc7.
> > Yes, we can get fixes into v5.12-rc7. Or v5.12-rc9...
>
> Yeah, I'm leaning toward not making it the default for 5.12-rc1 because
> not everything seems to be working, let's see how the rest of the week
> goes...
I think there's some value waiting until after rc1 to turn off if just
to find a few more issues.
Rob
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-02-10 16:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 15:43 [PATCH] clk: at91: Fix the declaration of the clocks Tudor Ambarus
2021-02-03 15:43 ` Tudor Ambarus
2021-02-03 18:15 ` Saravana Kannan
2021-02-03 18:15 ` Saravana Kannan
2021-02-04 12:46 ` Eugen.Hristev
2021-02-04 12:46 ` Eugen.Hristev
2021-02-04 13:54 ` Nicolas Ferre
2021-02-04 13:54 ` Nicolas Ferre
2021-02-08 9:49 ` Tudor.Ambarus
2021-02-08 9:49 ` Tudor.Ambarus
2021-02-10 0:54 ` Stephen Boyd
2021-02-10 0:54 ` Stephen Boyd
2021-02-10 0:56 ` Saravana Kannan
2021-02-10 0:56 ` Saravana Kannan
2021-02-10 8:51 ` Geert Uytterhoeven
2021-02-10 8:51 ` Geert Uytterhoeven
2021-02-10 8:57 ` Saravana Kannan
2021-02-10 8:57 ` Saravana Kannan
2021-02-10 9:10 ` Geert Uytterhoeven
2021-02-10 9:10 ` Geert Uytterhoeven
2021-02-10 9:00 ` Greg Kroah-Hartman
2021-02-10 9:00 ` Greg Kroah-Hartman
2021-02-10 16:22 ` Rob Herring [this message]
2021-02-10 16:22 ` Rob Herring
2021-02-10 0:56 ` Stephen Boyd
2021-02-10 0:56 ` Stephen Boyd
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=20210210162226.GA2246688@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=Claudiu.Beznea@microchip.com \
--cc=Codrin.Ciubotariu@microchip.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=Tudor.Ambarus@microchip.com \
--cc=a.fatoum@pengutronix.de \
--cc=alexandre.belloni@bootlin.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mirq-linux@rere.qmqm.pl \
--cc=mturquette@baylibre.com \
--cc=saravanak@google.com \
--cc=sboyd@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.