Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Robin Murphy <robin.murphy@arm.com>
To: Greg KH <greg@kroah.com>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
	Will Deacon <will@kernel.org>, Joerg Roedel <joro@8bytes.org>,
	Rob Clark <robdclark@gmail.com>, Yong Wu <yong.wu@mediatek.com>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	Orson Zhai <orsonzhai@gmail.com>,
	Baolin Wang <baolin.wang@linux.alibaba.com>,
	Chunyan Zhang <zhang.lyra@gmail.com>,
	Jean-Philippe Brucker <jean-philippe@linaro.org>
Subject: Re: Patch "iommu: Clean up open-coded ownership checks" has been added to the 6.6-stable tree
Date: Tue, 10 Dec 2024 12:26:21 +0000	[thread overview]
Message-ID: <c7446da1-11ca-4621-bc1a-8598e1a5a7fe@arm.com> (raw)
In-Reply-To: <2024121015-duke-dispose-ecec@gregkh>

On 2024-12-10 12:17 pm, Greg KH wrote:
> On Tue, Dec 10, 2024 at 12:09:42PM +0000, Robin Murphy wrote:
>> On 2024-12-09 11:27 am, Sasha Levin wrote:
>>> This is a note to let you know that I've just added the patch titled
>>>
>>>       iommu: Clean up open-coded ownership checks
>>>
>>> to the 6.6-stable tree which can be found at:
>>>       http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>>>
>>> The filename of the patch is:
>>>        iommu-clean-up-open-coded-ownership-checks.patch
>>> and it can be found in the queue-6.6 subdirectory.
>>>
>>> If you, or anyone else, feels it should not be added to the stable tree,
>>> please let <stable@vger.kernel.org> know about it.
>>
>> Unless you're also going to backport the rest of the larger redesign which
>> makes this commit message true, I don't think this is appropriate.
> 
> It's needed because of:
> 
>>>       Stable-dep-of: 229e6ee43d2a ("iommu/arm-smmu: Defer probe of clients after smmu device bound")
> 
> That commit.
> 
> Is this still not relevant?

It's not a functional dependency though, just context, and in this case 
I think a manual resolution is a lot safer to reason about. Lemme just 
remind myself how to write up a backport patch correctly, and I'll send 
it out shortly...

Cheers,
Robin.

> 
> thanks,
> 
> greg k-h


      reply	other threads:[~2024-12-10 12:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241209112746.3166260-1-sashal@kernel.org>
2024-12-10 12:09 ` Patch "iommu: Clean up open-coded ownership checks" has been added to the 6.6-stable tree Robin Murphy
2024-12-10 12:17   ` Greg KH
2024-12-10 12:26     ` Robin Murphy [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=c7446da1-11ca-4621-bc1a-8598e1a5a7fe@arm.com \
    --to=robin.murphy@arm.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=greg@kroah.com \
    --cc=jean-philippe@linaro.org \
    --cc=joro@8bytes.org \
    --cc=matthias.bgg@gmail.com \
    --cc=orsonzhai@gmail.com \
    --cc=robdclark@gmail.com \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=will@kernel.org \
    --cc=yong.wu@mediatek.com \
    --cc=zhang.lyra@gmail.com \
    /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