From: Sasha Levin <sashal@kernel.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Joerg Roedel <joro@8bytes.org>
Subject: Re: Patch "iommu/arm-smmu: Drop if with an always false condition" has been added to the 6.3-stable tree
Date: Sun, 21 May 2023 19:36:01 -0400 [thread overview]
Message-ID: <ZGqq4apFeKPMgUsd@sashalap> (raw)
In-Reply-To: <20230520144018.h6qqwvnsldawu4kx@pengutronix.de>
On Sat, May 20, 2023 at 04:40:18PM +0200, Uwe Kleine-König wrote:
>Hello,
>
>On Fri, May 19, 2023 at 09:49:37PM -0400, Sasha Levin wrote:
>> This is a note to let you know that I've just added the patch titled
>>
>> iommu/arm-smmu: Drop if with an always false condition
>>
>> to the 6.3-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-arm-smmu-drop-if-with-an-always-false-conditio.patch
>> and it can be found in the queue-6.3 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.
>
>I'd not add that patch to stable. It's just about dropping an
>
> if (false) {
> something();
> }
>
>The compiler probably isn't able to see that the condition is always
>false, so the only benefit is that the patch makes the compiled code a
>bit smaller.
Dropped, thanks!
--
Thanks,
Sasha
prev parent reply other threads:[~2023-05-21 23:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230520014938.2798196-1-sashal@kernel.org>
2023-05-20 14:40 ` Patch "iommu/arm-smmu: Drop if with an always false condition" has been added to the 6.3-stable tree Uwe Kleine-König
2023-05-21 23:36 ` Sasha Levin [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=ZGqq4apFeKPMgUsd@sashalap \
--to=sashal@kernel.org \
--cc=joro@8bytes.org \
--cc=robin.murphy@arm.com \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
--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