All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Alvin Šipraga" <alvin@pqrs.dk>
Cc: "Sasha Levin" <sashal@kernel.org>,
	stable@vger.kernel.org,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Andrew Lunn" <andrew@lunn.ch>,
	"Vivien Didelot" <vivien.didelot@gmail.com>,
	"Florian Fainelli" <f.fainelli@gmail.com>,
	"Vladimir Oltean" <olteanv@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	"Jakub Kicinski" <kuba@kernel.org>,
	"Michael Rasmussen" <mir@bang-olufsen.dk>,
	"Alvin Šipraga" <alsi@bang-olufsen.dk>,
	"Luiz Angelo Daros de Luca" <luizluca@gmail.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH stable 5.16+ 0/3] backported Realtek DSA driver fixes for 5.16 and 5.17
Date: Thu, 14 Apr 2022 13:03:02 +0200	[thread overview]
Message-ID: <Ylf/Zl9QL2M2+LYd@kroah.com> (raw)
In-Reply-To: <20220412173253.2247196-1-alvin@pqrs.dk>

On Tue, Apr 12, 2022 at 07:32:49PM +0200, Alvin Šipraga wrote:
> From: Alvin Šipraga <alsi@bang-olufsen.dk>
> 
> These fixes can be applied to both 5.16 and 5.17 - the subtree of
> drivers/net/dsa/realtek is identical save for a few unrelated places.
> 
> The main backporting effort was to remove some parts of the patches
> which touched the newly introduced MDIO interface, which was introduced
> in the 5.18 development cycle, and to work around a mass-rename of a
> single variable (smi -> priv). Regrettably this rename will make future
> stable backports equally tedious and hard to automate.
> 
> Please let me know if you would like me to send the series again for
> 5.17.

5.16 is now end-of-life, but I've queued these up for 5.17 now, thanks!

greg k-h

      parent reply	other threads:[~2022-04-14 11:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-12 17:32 [PATCH stable 5.16+ 0/3] backported Realtek DSA driver fixes for 5.16 and 5.17 Alvin Šipraga
2022-04-12 17:32 ` [PATCH stable 5.16+ 1/3] net: dsa: realtek: allow subdrivers to externally lock regmap Alvin Šipraga
2022-04-12 17:32 ` [PATCH stable 5.16+ 2/3] net: dsa: realtek: rtl8365mb: serialize indirect PHY register access Alvin Šipraga
2022-04-12 17:32 ` [PATCH stable 5.16+ 3/3] net: dsa: realtek: make interface drivers depend on OF Alvin Šipraga
2022-04-14 11:03 ` 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=Ylf/Zl9QL2M2+LYd@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alsi@bang-olufsen.dk \
    --cc=alvin@pqrs.dk \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luizluca@gmail.com \
    --cc=mir@bang-olufsen.dk \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=vivien.didelot@gmail.com \
    /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.