From: Nicolin Chen <nicolinc@nvidia.com>
To: Baolu Lu <baolu.lu@linux.intel.com>, Will Deacon <will@kernel.org>
Cc: <robin.murphy@arm.com>, <joro@8bytes.org>, <jgg@nvidia.com>,
<jean-philippe@linaro.org>, <apopple@nvidia.com>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <iommu@lists.linux.dev>,
<stable@vger.kernel.org>
Subject: Re: [PATCH] iommu/arm-smmu-v3: Fix soft lockup triggered by arm_smmu_mm_invalidate_range
Date: Mon, 18 Sep 2023 07:58:39 -0700 [thread overview]
Message-ID: <ZQhln3EQ5DeXhfEU@Asurada-Nvidia> (raw)
In-Reply-To: <20230918092341.GB17341@willie-the-truck>
On Mon, Sep 18, 2023 at 10:23:42AM +0100, Will Deacon wrote:
> > If the patch does not apply to any stable kernel that you want it to be
> > there, you can then post a back-ported patch to the stable mailing list.
> >
> > When doing so, it's better to include the following information:
> >
> > - The mainline commit ID of the back-ported patch.
> > - The versions of the stable kernel(s) to which you want the back-ported
> > patch to be applied.
> >
> > Hope this helps.
Yes! Thanks :)
> Yup, please send a version against -rc1 so we can land that first.
Yea, will send a new version.
Thank you
Nicolin
next prev parent reply other threads:[~2023-09-18 15:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 20:39 [PATCH] iommu/arm-smmu-v3: Fix soft lockup triggered by arm_smmu_mm_invalidate_range Nicolin Chen
2023-09-15 7:43 ` Nicolin Chen
2023-09-18 5:33 ` Baolu Lu
2023-09-18 9:23 ` Will Deacon
2023-09-18 14:58 ` Nicolin Chen [this message]
2023-09-18 9:22 ` Will Deacon
2023-09-18 15:09 ` Nicolin Chen
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=ZQhln3EQ5DeXhfEU@Asurada-Nvidia \
--to=nicolinc@nvidia.com \
--cc=apopple@nvidia.com \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jean-philippe@linaro.org \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox