From: Baolu Lu <baolu.lu@linux.intel.com>
To: Nicolin Chen <nicolinc@nvidia.com>,
will@kernel.org, robin.murphy@arm.com
Cc: baolu.lu@linux.intel.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 13:33:31 +0800 [thread overview]
Message-ID: <9334dfcd-7749-6ae1-1170-b4952f2b8181@linux.intel.com> (raw)
In-Reply-To: <ZQQLNmmAOsNmvtDs@Asurada-Nvidia>
On 9/15/23 3:43 PM, Nicolin Chen wrote:
> I found this patch cannot be applied to v6.6-rc1 due to conflicts
> with some new commits that were merged during the previous cycle.
>
> I can redo a version rebasing on the v6.6-rc1, yet the new version
> won't apply to earlier kernel stable trees. Is there a way to make
> it happen that both mainline and earlier trees can have this fix?
Normally, bug fixes should first be submitted to the mainline kernel
(also known as Linus's tree). If you use the "Fixes" and "CC-stable"
tags, the patch will be automatically picked up for the appropriate
stable kernels.
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.
Best regards,
baolu
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-09-18 5:37 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 [this message]
2023-09-18 9:23 ` Will Deacon
2023-09-18 14:58 ` Nicolin Chen
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=9334dfcd-7749-6ae1-1170-b4952f2b8181@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=apopple@nvidia.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=nicolinc@nvidia.com \
--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;
as well as URLs for NNTP newsgroup(s).