From: Pavel Machek <pavel@denx.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
nathan@kernel.org, andrii@kernel.org,
dave.stevenson@raspberrypi.com
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de
Subject: Re: [PATCH 5.15 000/731] 5.15.86-rc1 review
Date: Thu, 29 Dec 2022 15:40:51 +0100 [thread overview]
Message-ID: <Y62m85tYWONgSWmm@duo.ucw.cz> (raw)
In-Reply-To: <20221228144256.536395940@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 1415 bytes --]
Hi!
> This is the start of the stable review cycle for the 5.15.86 release.
> There are 731 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
These are just kCFI annotations. I don't believe we need them in 5.10
(and 5.15).
> Nathan Chancellor <nathan@kernel.org>
> net: ethernet: ti: Fix return type of netcp_ndo_start_xmit()
> Nathan Chancellor <nathan@kernel.org>
> drm/fsl-dcu: Fix return type of fsl_dcu_drm_connector_mode_valid()
> Nathan Chancellor <nathan@kernel.org>
> drm/sti: Fix return type of sti_{dvo,hda,hdmi}_connector_mode_valid()
These are just preparation for "bpf: allow precision tracking for
programs with subprogs", but that is not queued here. We should not
need them.
> Andrii Nakryiko <andrii@kernel.org>
> bpf: propagate precision in ALU/ALU64 operations
> Andrii Nakryiko <andrii@kernel.org>
> bpf: propagate precision across all frames, not just the last one
AFAICT, DRM_FORMAT_P030 is not used anywhere in 5.15, so we should not
need this one.
> Dave Stevenson <dave.stevenson@raspberrypi.com>
> drm/fourcc: Add packed 10bit YUV 4:2:0 format
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2022-12-29 14:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 14:31 [PATCH 5.15 000/731] 5.15.86-rc1 review Greg Kroah-Hartman
2022-12-28 19:08 ` Florian Fainelli
2022-12-28 20:42 ` Slade Watkins
2022-12-29 3:42 ` Bagas Sanjaya
2022-12-29 3:50 ` Ron Economos
2022-12-29 7:38 ` Thierry Reding
2022-12-29 7:43 ` Thierry Reding
2022-12-29 7:54 ` Thierry Reding
2022-12-29 13:42 ` Guenter Roeck
2022-12-29 14:40 ` Pavel Machek [this message]
2022-12-29 16:56 ` Nathan Chancellor
2022-12-29 23:26 ` Shuah Khan
2022-12-30 7:28 ` Naresh Kamboju
-- strict thread matches above, loose matches on Subject: below --
2022-12-29 4:00 Daniel Díaz
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=Y62m85tYWONgSWmm@duo.ucw.cz \
--to=pavel@denx.de \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=dave.stevenson@raspberrypi.com \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=nathan@kernel.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--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