On Mon, Feb 18, 2019 at 3:15 PM Simon Horman <horms@xxxxxxxxxxxx> 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@xxxxxxxxxxxx> 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@xxxxxxxxxxxx> 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@xxxxxxxxxx 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
