From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: stable <stable@vger.kernel.org>, Sasha Levin <sashal@kernel.org>,
Aurelien Jarno <aurelien@aurel32.net>,
David Laight <David.Laight@aculab.com>,
Jiri Slaby <jirislaby@gmail.com>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Please apply commit 31e97d7c9ae3 ("media: solo6x10: replace max(a, min(b, c)) by clamp(b, a, c)") to 6.1.y
Date: Fri, 23 Aug 2024 06:55:19 +0800 [thread overview]
Message-ID: <2024082346-strobe-balance-68ec@gregkh> (raw)
In-Reply-To: <ZsdzH-n9-9K8XYSx@eldamar.lan>
On Thu, Aug 22, 2024 at 07:19:27PM +0200, Salvatore Bonaccorso wrote:
> Hi
>
> While building 6.1.106 based verson for Debian I noticed that all
> 32bit architectures did fail to build:
>
> https://buildd.debian.org/status/fetch.php?pkg=linux&arch=i386&ver=6.1.106-1&stamp=1724307428&raw=0
>
> The problem is known as
>
> https://lore.kernel.org/lkml/18c6df0d-45ed-450c-9eda-95160a2bbb8e@gmail.com/
>
> This now affects as well 6.1.y as the commits 867046cc7027 ("minmax:
> relax check to allow comparison between unsigned arguments and signed
> constants") and 4ead534fba42 ("minmax: allow comparisons of 'int'
> against 'unsigned char/short'") were backported to 6.1.106.
>
> Thus, can you please pick as well 31e97d7c9ae3 ("media: solo6x10:
> replace max(a, min(b, c)) by clamp(b, a, c)") for 6.1.y?
>
> Note I suspect it is required as well for 5.15.164 (as the commits
> were backported there as well and 31e97d7c9ae3 now missing there).
Now queued up, thanks!
greg k-h
prev parent reply other threads:[~2024-08-22 22:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 17:19 Please apply commit 31e97d7c9ae3 ("media: solo6x10: replace max(a, min(b, c)) by clamp(b, a, c)") to 6.1.y Salvatore Bonaccorso
2024-08-22 22:55 ` Greg Kroah-Hartman [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=2024082346-strobe-balance-68ec@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=David.Laight@aculab.com \
--cc=aurelien@aurel32.net \
--cc=carnil@debian.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jirislaby@gmail.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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