Message ID | cover.1549622472.git.horms+renesas@verge.net.au (mailing list archive) |
---|---|
State | Not Applicable |
Delegated to: | Simon Horman |
Headers | show |
Series | [GIT,PULL] Renesas ARM Based SoC Updates for v5.1 | expand |
On Fri, Feb 8, 2019 at 12:14 PM Simon Horman <horms+renesas@verge.net.au> wrote: > > Hi Olof, Hi Kevin, Hi Arnd, > > Please consider these Renesas ARM based SoC updates for v5.1. > > > The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c: > > Linux 5.0-rc1 (2019-01-06 17:08:20 -0800) > > are available in the git repository at: > > https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-arm-soc-for-v5.1 > > for you to fetch changes up to 5347a0203709d5039a74d7c94e23519eee478094: > > ARM: shmobile: Fix R-Car Gen2 regulator quirk (2019-01-07 13:24:07 +0100) > > ---------------------------------------------------------------- > Renesas ARM Based SoC Updates for v5.1 > > * Correct shared IRQ handling of R-Car Gen2 Regulator quirk > * Add missing dts files to MAINTAINERS Should the bugfix be marked Cc:stable and and Fixes:... ? Pulled into arm/soc, thanks! Arnd
On Fri, Feb 15, 2019 at 05:49:32PM +0100, Arnd Bergmann wrote: > On Fri, Feb 8, 2019 at 12:14 PM Simon Horman <horms+renesas@verge.net.au> wrote: > > > > Hi Olof, Hi Kevin, Hi Arnd, > > > > Please consider these Renesas ARM based SoC updates for v5.1. > > > > > > The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c: > > > > Linux 5.0-rc1 (2019-01-06 17:08:20 -0800) > > > > are available in the git repository at: > > > > https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-arm-soc-for-v5.1 > > > > for you to fetch changes up to 5347a0203709d5039a74d7c94e23519eee478094: > > > > ARM: shmobile: Fix R-Car Gen2 regulator quirk (2019-01-07 13:24:07 +0100) > > > > ---------------------------------------------------------------- > > Renesas ARM Based SoC Updates for v5.1 > > > > * Correct shared IRQ handling of R-Car Gen2 Regulator quirk > > * Add missing dts files to MAINTAINERS > > Should the bugfix be marked Cc:stable and and Fixes:... ? > > Pulled into arm/soc, thanks! Thanks, Sorry for missing that, I think that the bugfix should have had the following. Let me know if/how you want to handle updating the patch's changelog. Fixes: 6d14d4d313d09dab ("ARM: shmobile: Rework the PMIC IRQ line quirk")
On Mon, Feb 18, 2019 at 12:27 PM Simon Horman <horms@verge.net.au> wrote: > On Fri, Feb 15, 2019 at 05:49:32PM +0100, Arnd Bergmann wrote: > > On Fri, Feb 8, 2019 at 12:14 PM Simon Horman <horms+renesas@verge.net.au> wrote: > > > Renesas ARM Based SoC Updates for v5.1 > > > > > > * Correct shared IRQ handling of R-Car Gen2 Regulator quirk > > > * Add missing dts files to MAINTAINERS > > > > Should the bugfix be marked Cc:stable and and Fixes:... ? > > > Sorry for missing that, I think that the bugfix should have had the following. > Let me know if/how you want to handle updating the patch's changelog. > > Fixes: 6d14d4d313d09dab ("ARM: shmobile: Rework the PMIC IRQ line quirk") I think the easiest way is to send an email to stable@kernel.org asking for a backport of commit 5347a0203709 ("ARM: shmobile: Fix R-Car Gen2 regulator quirk") after that has hit the mainline kernel and asking for a backport. I've added it to Cc here, but I don't know if that's sufficient. If you'd rather have me pick up the patch for 5.0 as well, I can also do that and add the Cc/Fixes lines there. We will then have a duplicate commit in 5.1, but it should not cause any merge issues. Arnd
On Mon, Feb 18, 2019 at 02:12:07PM +0100, Arnd Bergmann wrote: > On Mon, Feb 18, 2019 at 12:27 PM Simon Horman <horms@verge.net.au> wrote: > > On Fri, Feb 15, 2019 at 05:49:32PM +0100, Arnd Bergmann wrote: > > > On Fri, Feb 8, 2019 at 12:14 PM Simon Horman <horms+renesas@verge.net.au> wrote: > > > > Renesas ARM Based SoC Updates for v5.1 > > > > > > > > * Correct shared IRQ handling of R-Car Gen2 Regulator quirk > > > > * Add missing dts files to MAINTAINERS > > > > > > Should the bugfix be marked Cc:stable and and Fixes:... ? > > > > > Sorry for missing that, I think that the bugfix should have had the following. > > Let me know if/how you want to handle updating the patch's changelog. > > > > Fixes: 6d14d4d313d09dab ("ARM: shmobile: Rework the PMIC IRQ line quirk") > > I think the easiest way is to send an email to stable@kernel.org asking for > a backport of commit 5347a0203709 ("ARM: shmobile: Fix R-Car Gen2 regulator > quirk") after that has hit the mainline kernel and asking for a backport. > > I've added it to Cc here, but I don't know if that's sufficient. > > If you'd rather have me pick up the patch for 5.0 as well, I can also do > that and add the Cc/Fixes lines there. We will then have a duplicate > commit in 5.1, but it should not cause any merge issues. Thanks Arnd, I'm happy to handle this via stable and avoid the duplicate. If I don't hear back from them in a few days I'll make a formal submission there.
On Mon, Feb 18, 2019 at 3:15 PM Simon Horman <horms@verge.net.au> wrote: > > On Mon, Feb 18, 2019 at 02:12:07PM +0100, Arnd Bergmann wrote: > > On Mon, Feb 18, 2019 at 12:27 PM Simon Horman <horms@verge.net.au> wrote: > > > On Fri, Feb 15, 2019 at 05:49:32PM +0100, Arnd Bergmann wrote: > > > > On Fri, Feb 8, 2019 at 12:14 PM Simon Horman <horms+renesas@verge.net.au> wrote: > > > > > Renesas ARM Based SoC Updates for v5.1 > > > > > > > > > > * Correct shared IRQ handling of R-Car Gen2 Regulator quirk > > > > > * Add missing dts files to MAINTAINERS > > > > > > > > Should the bugfix be marked Cc:stable and and Fixes:... ? > > > > > > > Sorry for missing that, I think that the bugfix should have had the following. > > > Let me know if/how you want to handle updating the patch's changelog. > > > > > > Fixes: 6d14d4d313d09dab ("ARM: shmobile: Rework the PMIC IRQ line quirk") > > > > I think the easiest way is to send an email to stable@kernel.org asking for > > a backport of commit 5347a0203709 ("ARM: shmobile: Fix R-Car Gen2 regulator > > quirk") after that has hit the mainline kernel and asking for a backport. > > > > I've added it to Cc here, but I don't know if that's sufficient. > > > > If you'd rather have me pick up the patch for 5.0 as well, I can also do > > that and add the Cc/Fixes lines there. We will then have a duplicate > > commit in 5.1, but it should not cause any merge issues. > > Thanks Arnd, > > I'm happy to handle this via stable and avoid the duplicate. > If I don't hear back from them in a few days I'll make a formal > submission there. Ok, sounds good. To clarify: I think you should only write them /after/ the commit is in mainline then, i.e. near the end of the 5.1 merge window. Arnd
On Mon, Feb 18, 2019 at 03:21:14PM +0100, Arnd Bergmann wrote: > On Mon, Feb 18, 2019 at 3:15 PM Simon Horman <horms@verge.net.au> wrote: > > > > On Mon, Feb 18, 2019 at 02:12:07PM +0100, Arnd Bergmann wrote: > > > On Mon, Feb 18, 2019 at 12:27 PM Simon Horman <horms@verge.net.au> wrote: > > > > On Fri, Feb 15, 2019 at 05:49:32PM +0100, Arnd Bergmann wrote: > > > > > On Fri, Feb 8, 2019 at 12:14 PM Simon Horman <horms+renesas@verge.net.au> wrote: > > > > > > Renesas ARM Based SoC Updates for v5.1 > > > > > > > > > > > > * Correct shared IRQ handling of R-Car Gen2 Regulator quirk > > > > > > * Add missing dts files to MAINTAINERS > > > > > > > > > > Should the bugfix be marked Cc:stable and and Fixes:... ? > > > > > > > > > Sorry for missing that, I think that the bugfix should have had the following. > > > > Let me know if/how you want to handle updating the patch's changelog. > > > > > > > > Fixes: 6d14d4d313d09dab ("ARM: shmobile: Rework the PMIC IRQ line quirk") > > > > > > I think the easiest way is to send an email to stable@kernel.org asking for > > > a backport of commit 5347a0203709 ("ARM: shmobile: Fix R-Car Gen2 regulator > > > quirk") after that has hit the mainline kernel and asking for a backport. > > > > > > I've added it to Cc here, but I don't know if that's sufficient. > > > > > > If you'd rather have me pick up the patch for 5.0 as well, I can also do > > > that and add the Cc/Fixes lines there. We will then have a duplicate > > > commit in 5.1, but it should not cause any merge issues. > > > > Thanks Arnd, > > > > I'm happy to handle this via stable and avoid the duplicate. > > If I don't hear back from them in a few days I'll make a formal > > submission there. > > Ok, sounds good. > > To clarify: I think you should only write them /after/ the commit > is in mainline then, i.e. near the end of the 5.1 merge window. Thanks Arnd, got it.