All of lore.kernel.org
 help / color / mirror / Atom feed
From: Klaus Kudielka <klaus.kudielka@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, stable@vger.kernel.org
Subject: Re: [PATCH 6.1 0000/1140] 6.1.2-rc2 review
Date: Sat, 31 Dec 2022 10:10:05 +0100	[thread overview]
Message-ID: <e9ee0609520238d28d94ee8b66e20ac0c6069caa.camel@gmail.com> (raw)
In-Reply-To: <20221230094107.317705320@linuxfoundation.org>

On Fri, 2022-12-30 at 10:49 +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.1.2 release.
> There are 1140 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.
> 
> Responses should be made by Sun, 01 Jan 2023 09:38:41 +0000.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
>         https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.1.2-rc2.gz
> or in the git tree and branch at:
>         git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.1.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h
> 
> 

Hi Greg,

I'm concerned about backporting those two commits to *any* stable kernel right now:

> Pali Rohár <pali@kernel.org>
>     ARM: dts: armada-39x: Fix compatible string for gpios
[ Upstream commit d10886a4e6f85ee18d47a1066a52168461370ded ]

> 
> Pali Rohár <pali@kernel.org>
>     ARM: dts: armada-38x: Fix compatible string for gpios
[ Upstream commit c4de4667f15d04ef5920bacf41e514ec7d1ef03d ]

The latter one breaks my Turris Omnia (Armada 385) pretty badly, and I guess we will end
up with similar problems on Armada 39x boards.

Link: https://lore.kernel.org/r/f24474e70c1a4e9692bd596ef6d97ceda9511245.camel@gmail.com/

Thanks, Klaus


  parent reply	other threads:[~2022-12-31  9:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-30  9:49 [PATCH 6.1 0000/1140] 6.1.2-rc2 review Greg Kroah-Hartman
2022-12-30 14:38 ` Rudi Heitbaum
2022-12-30 17:01 ` Thierry Reding
2022-12-30 17:04 ` Slade Watkins
2022-12-30 21:08 ` Florian Fainelli
2022-12-31  0:18 ` Guenter Roeck
2022-12-31  8:31 ` Bagas Sanjaya
2022-12-31  9:10 ` Klaus Kudielka [this message]
2022-12-31  9:35   ` Greg Kroah-Hartman
2022-12-31  9:43 ` Naresh Kamboju
2022-12-31 10:56 ` Ron Economos
2022-12-30 16:42 Ronald Warsow

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=e9ee0609520238d28d94ee8b66e20ac0c6069caa.camel@gmail.com \
    --to=klaus.kudielka@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.