On Mon, Jul 22, 2019 at 04:02:18PM +0000, Derrick, Jonathan wrote:
> On Fri, 2019-06-21 at 15:28 +0100, Lorenzo Pieralisi wrote:
> > [dropped CC stable]
> >
> > On Tue, Jun 11, 2019 at 03:15:38PM -0600, Jon Derrick wrote:
> > > VMD config space addressing relies on mapping the BDF of the target into
> > > the VMD config bar. When using bus number offsets to number the VMD
> > > domain, the offset needs to be ignored in order to correctly map devices
> > > to their config space.
> > >
> > > Fixes: 2a5a9c9a20f9 ("PCI: vmd: Add offset to bus numbers if necessary")
> > > Cc: <stable@xxxxxxxxxxxxxxx> # v4.19
> > > Cc: <stable@xxxxxxxxxxxxxxx> # v4.18
> >
> > Hi Jon,
> >
> > that's not how stable should be handled. You should always start
> > by fixing mainline and if there are backports to be fixed too you
> > should add patch dependencies in the CC area, see:
> >
> > Documentation/process/stable-kernel-rules.rst
> >
> > Never add stable to the CC list in the email header, only in the
> > commit log.
> >
> > When your patch hits mainline it will trickle back into stable,
> > if you specified dependencies as described above there is nothing
> > to do.
> >
> > Thanks,
> > Lorenzo
> >
>
> Besides the stable issue, can we get this into 5.3?
Usually we send fixes at -rc for patches that were merged in the
previous merge window; this fix is not one of those so I think
we will send it for v5.4 unless it is very urgent.
We should still update stable info in the log appropriately
before queuing it.
Thanks,
Lorenzo
