From: Stefan Wahren <stefan.wahren@i2se.com> To: Maxime Ripard <maxime@cerno.tech>, Guillaume Gardet <Guillaume.Gardet@arm.com> Cc: "Ivan T. Ivanov" <iivanov@suse.de>, Michael Turquette <mturquette@baylibre.com>, Stephen Boyd <sboyd@kernel.org>, Nicolas Saenz Julienne <nsaenz@kernel.org>, Dave Stevenson <dave.stevenson@raspberrypi.com>, "bcm-kernel-feedback-list@broadcom.com" <bcm-kernel-feedback-list@broadcom.com>, "linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>, "linux-rpi-kernel@lists.infradead.org" <linux-rpi-kernel@lists.infradead.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, nd <nd@arm.com> Subject: Re: [PATCH v4 0/3] clk: bcm: rpi: Add support for three more clocks Date: Wed, 11 May 2022 08:10:50 +0200 [thread overview] Message-ID: <6066bd9d-b53b-0a91-7440-98244c2d55c2@i2se.com> (raw) In-Reply-To: <20220510133019.h2urxj3feponfuku@houat> Am 10.05.22 um 15:30 schrieb Maxime Ripard: > Hi, > > On Tue, May 10, 2022 at 01:20:18PM +0000, Guillaume Gardet wrote: >> May I ask what's the status/plan of this patch series? > As far as I know it hasn't been merged yet. > >> It seems it has not been merged yet, and I know we are a bit late in >> the 5.18 schedule, but I think this is a good fix for 5.18. > Fix for what? I don't think this series fix any bug? This seems to be a "fix" for the Frankenstone scenario: mainline kernel + vendor DT >> And, this looks like to be a good candidate for a backport to stable >> kernels. > This is not going to be trivial to backmerge, it depends on 12c90f3f27bb > that isn't marked for stable I don't think this is a good idea to backmerge these changes. Best regards > > maxime > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Stefan Wahren <stefan.wahren@i2se.com> To: Maxime Ripard <maxime@cerno.tech>, Guillaume Gardet <Guillaume.Gardet@arm.com> Cc: "Ivan T. Ivanov" <iivanov@suse.de>, Michael Turquette <mturquette@baylibre.com>, Stephen Boyd <sboyd@kernel.org>, Nicolas Saenz Julienne <nsaenz@kernel.org>, Dave Stevenson <dave.stevenson@raspberrypi.com>, "bcm-kernel-feedback-list@broadcom.com" <bcm-kernel-feedback-list@broadcom.com>, "linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>, "linux-rpi-kernel@lists.infradead.org" <linux-rpi-kernel@lists.infradead.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, nd <nd@arm.com> Subject: Re: [PATCH v4 0/3] clk: bcm: rpi: Add support for three more clocks Date: Wed, 11 May 2022 08:10:50 +0200 [thread overview] Message-ID: <6066bd9d-b53b-0a91-7440-98244c2d55c2@i2se.com> (raw) In-Reply-To: <20220510133019.h2urxj3feponfuku@houat> Am 10.05.22 um 15:30 schrieb Maxime Ripard: > Hi, > > On Tue, May 10, 2022 at 01:20:18PM +0000, Guillaume Gardet wrote: >> May I ask what's the status/plan of this patch series? > As far as I know it hasn't been merged yet. > >> It seems it has not been merged yet, and I know we are a bit late in >> the 5.18 schedule, but I think this is a good fix for 5.18. > Fix for what? I don't think this series fix any bug? This seems to be a "fix" for the Frankenstone scenario: mainline kernel + vendor DT >> And, this looks like to be a good candidate for a backport to stable >> kernels. > This is not going to be trivial to backmerge, it depends on 12c90f3f27bb > that isn't marked for stable I don't think this is a good idea to backmerge these changes. Best regards > > maxime > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel _______________________________________________ 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:[~2022-05-11 6:11 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-28 6:57 [PATCH v4 0/3] clk: bcm: rpi: Add support for three more clocks Ivan T. Ivanov 2022-04-28 6:57 ` Ivan T. Ivanov 2022-04-28 6:57 ` [PATCH v4 1/3] clk: bcm: rpi: Add support HEVC clock Ivan T. Ivanov 2022-04-28 6:57 ` Ivan T. Ivanov 2022-04-28 6:57 ` [PATCH v4 2/3] clk: bcm: rpi: Handle pixel clock in firmware Ivan T. Ivanov 2022-04-28 6:57 ` Ivan T. Ivanov 2022-04-28 6:57 ` [PATCH v4 3/3] clk: bcm: rpi: Add support for VEC clock Ivan T. Ivanov 2022-04-28 6:57 ` Ivan T. Ivanov 2022-04-28 8:03 ` Maxime Ripard 2022-04-28 8:03 ` Maxime Ripard 2022-05-10 13:20 ` [PATCH v4 0/3] clk: bcm: rpi: Add support for three more clocks Guillaume Gardet 2022-05-10 13:20 ` Guillaume Gardet 2022-05-10 13:30 ` Maxime Ripard 2022-05-10 13:30 ` Maxime Ripard 2022-05-11 6:10 ` Stefan Wahren [this message] 2022-05-11 6:10 ` Stefan Wahren 2022-05-12 7:57 ` Maxime Ripard 2022-05-12 7:57 ` Maxime Ripard 2022-05-12 8:10 ` Ivan Ivanov 2022-05-12 8:53 ` Maxime Ripard 2022-05-12 8:53 ` Maxime Ripard 2022-05-12 9:03 ` Ivan Ivanov 2022-07-10 11:12 ` Stefan Wahren 2022-07-10 11:12 ` Stefan Wahren 2022-07-11 7:02 ` Ivan T. Ivanov 2022-07-11 7:02 ` Ivan T. Ivanov 2022-07-11 11:55 ` Stefan Wahren 2022-07-11 11:55 ` Stefan Wahren 2022-08-23 22:54 ` Stephen Boyd 2022-05-26 11:36 ` Ivan T. Ivanov 2022-05-26 11:36 ` Ivan T. Ivanov 2022-06-21 15:30 ` Florian Fainelli 2022-06-21 15:30 ` Florian Fainelli
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=6066bd9d-b53b-0a91-7440-98244c2d55c2@i2se.com \ --to=stefan.wahren@i2se.com \ --cc=Guillaume.Gardet@arm.com \ --cc=bcm-kernel-feedback-list@broadcom.com \ --cc=dave.stevenson@raspberrypi.com \ --cc=iivanov@suse.de \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-clk@vger.kernel.org \ --cc=linux-rpi-kernel@lists.infradead.org \ --cc=maxime@cerno.tech \ --cc=mturquette@baylibre.com \ --cc=nd@arm.com \ --cc=nsaenz@kernel.org \ --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: linkBe 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.