public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Easwar Hariharan <eahariha@linux.microsoft.com>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org, Robin Murphy <robin.murphy@arm.com>,
	Rui Zhu <zhurui3@huawei.com>, Will Deacon <will@kernel.org>
Subject: Re: [PATCH 6.5] iommu/arm-smmu-v3: Avoid constructing invalid range commands
Date: Tue, 10 Oct 2023 09:32:29 -0700	[thread overview]
Message-ID: <edf2c4fd-985c-48aa-9476-e6248ca8aba3@linux.microsoft.com> (raw)
In-Reply-To: <ZSARLoAx_mPkrG8f@sashalap>

On 10/6/23 06:52, Sasha Levin wrote:
<snip>
> Queued this and the ones for older kernels. In general, if it's just a
> cherrypick, please just list commit ids as it makes our lives much
> easier :)
> 

Will do for next time. :)

-- 
Thanks,
Easwar


      reply	other threads:[~2023-10-10 16:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-05 19:34 [PATCH 6.5] iommu/arm-smmu-v3: Avoid constructing invalid range commands Easwar Hariharan
2023-10-06 13:52 ` Sasha Levin
2023-10-10 16:32   ` Easwar Hariharan [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=edf2c4fd-985c-48aa-9476-e6248ca8aba3@linux.microsoft.com \
    --to=eahariha@linux.microsoft.com \
    --cc=robin.murphy@arm.com \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=will@kernel.org \
    --cc=zhurui3@huawei.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