stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: "Pali Rohár" <pali@kernel.org>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Marek Behún" <kabel@kernel.org>,
	stable@vger.kernel.org
Subject: Re: Backporting armada-3700-rwtm-firmware DTS changes to stable kernel
Date: Tue, 20 Jul 2021 19:03:49 -0400	[thread overview]
Message-ID: <YPdWVTB0tWvsgKR3@sashalap> (raw)
In-Reply-To: <20210720222559.k4zoqr2rk62pj7ky@pali>

On Wed, Jul 21, 2021 at 12:25:59AM +0200, Pali Rohár wrote:
>Hello Greg & Sasha, I would like to ask you for your opinion about
>backporting DTS patches to stable kernel which allows usage of hwrng on
>Marvell Armada 3700 devices.
>
>Driver is already part of 5.4 kernel, just DTS bindings are not there.
>I do not know if such backport is suitable for stable kernels. In file
>https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
>is written that "New device IDs and quirks are also accepted" where
>"device id" could mean also small DTS change...

We could, that's how I've been parsing that rule.

>What do you think? Question is about these 3 small commits:
>https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=90ae47215de3fec862aeb1a0f0e28bb505ab1351
>https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=46d2f6d0c99f7f95600e633c7dc727745faaf95e
>https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3a52a48973b355b3aac5add92ef50650ae37c2bd

If it was actually tested on 5.4, I could queue it up for the next
release cycle.

-- 
Thanks,
Sasha

  reply	other threads:[~2021-07-20 23:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-20 22:25 Backporting armada-3700-rwtm-firmware DTS changes to stable kernel Pali Rohár
2021-07-20 23:03 ` Sasha Levin [this message]
2021-07-21 13:21   ` Pali Rohár
2021-07-21 13:54     ` Sasha Levin

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=YPdWVTB0tWvsgKR3@sashalap \
    --to=sashal@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kabel@kernel.org \
    --cc=pali@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).