On Mon, Jul 29, 2019 at 05:50:35PM +0100, Dmitry Safonov wrote:
> Hi Greg,
>
> On 7/29/19 5:19 PM, gregkh@xxxxxxxxxxxxxxxxxxx wrote:
> >
> > The patch below does not apply to the 4.9-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@xxxxxxxxxxxxxxx>.
>
> It's not needed for v4.9 stable tree [as pointed by tag's comment line]:
>
> > Cc: <stable@xxxxxxxxxxxxxxx> # 4.14+
>
> If there is any better way to inform where a commit should be
> backported, please let me know.
That is correct, as this commit (13cf01744608 ("iommu/vt-d: Make use of
iova deferred flushing")) did originally show up in 4.14:
$ git describe --contains 13cf01744608
v4.14-rc1~72^2^14~3
But, that commit ended up in a stable release, the 4.9.104 release.
Oh. nope, crap, my fault, my scripts pick up the fact that we refer to
commit 13cf01744608 in a 4.9 commit, but only the fact that it is _not_
in the 4.9.y tree.
Sorry, my fault, scripts are only so good at times.
> I'll send v4.19 -stable patch shortly..
> And will prepare v4.14 patch (as we don't have v4.14 release, I need to
> actually port it).
Thanks for doing the backport, and sorry for the 4.9.y noise, you were
right here, my scripts were wrong.
greg k-h
