From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nadav Amit <namit@vmware.com>
Cc: Lu Baolu <baolu.lu@linux.intel.com>,
David Woodhouse <dwmw2@infradead.org>,
Joerg Roedel <joro@8bytes.org>,
"jroedel@suse.de" <jroedel@suse.de>,
Will Deacon <will@kernel.org>, stable <stable@vger.kernel.org>
Subject: Re: FAILED: patch "[PATCH] iommu/vt-d: Do not use flush-queue when caching-mode is on" failed to apply to 5.10-stable tree
Date: Mon, 8 Feb 2021 13:43:23 +0100 [thread overview]
Message-ID: <YCEx614XHUA8oaUr@kroah.com> (raw)
In-Reply-To: <803F8779-E4A5-43D9-9AAB-A64C763731B7@vmware.com>
On Fri, Feb 05, 2021 at 06:29:27PM +0000, Nadav Amit wrote:
> > On Feb 5, 2021, at 12:54 AM, Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> >
> > On Thu, Feb 04, 2021 at 06:04:13PM +0000, Nadav Amit wrote:
> >> Backporting requires to disable strict during initialization. Lu, can
> >> you ack this patch?
> >>
> > This works for 5.10, thanks! But what about 4.9, 4.14, 4.19, and 5.4?
> > Those also need this change, right?
>
> Thanks for taking the patch.
>
> Yes, older kernels need to be patched too. I wanted Lu to ack the 5.10 patch
> first.
>
> For 5.4 and older kernels, the patch is fundamentally the same as the one
> for 5.10. Yet the patch that I sent for 5.10 does not apply cleanly, so
> please use the following patch.
>
> Please let me know if there is any problem.
>
That worked, thanks.
greg k-h
prev parent reply other threads:[~2021-02-08 12:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1612104088214157@kroah.com>
2021-02-04 18:04 ` FAILED: patch "[PATCH] iommu/vt-d: Do not use flush-queue when caching-mode is on" failed to apply to 5.10-stable tree Nadav Amit
2021-02-05 1:16 ` Lu Baolu
2021-02-05 8:54 ` Greg Kroah-Hartman
2021-02-05 18:29 ` Nadav Amit
2021-02-08 12:43 ` Greg Kroah-Hartman [this message]
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=YCEx614XHUA8oaUr@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=baolu.lu@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=joro@8bytes.org \
--cc=jroedel@suse.de \
--cc=namit@vmware.com \
--cc=stable@vger.kernel.org \
--cc=will@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: link
Be 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.