From: Jakub Kicinski <kuba@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>, Andy Chiu <andy.chiu@sifive.com>
Cc: radhey.shyam.pandey@xilinx.com, robert.hancock@calian.com,
michal.simek@xilinx.com, davem@davemloft.net, pabeni@redhat.com,
robh+dt@kernel.org, linux@armlinux.org.uk,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
robh@kernel.org, Greentime Hu <greentime.hu@sifive.com>
Subject: Re: [PATCH v7 net 4/4] net: axiemac: use a phandle to reference pcs_phy
Date: Tue, 29 Mar 2022 18:48:19 -0700 [thread overview]
Message-ID: <20220329184819.6d4354b6@kernel.org> (raw)
In-Reply-To: <YkOxexKUQqmFVe9l@lunn.ch>
On Wed, 30 Mar 2022 03:25:15 +0200 Andrew Lunn wrote:
> > I'm not sure if this is a fix or adding support for a new configuration.
> > Andrew, WDYT?
>
> I guess it fails this stable rule:
>
> It must fix a problem that causes a build error (but not for things
> marked CONFIG_BROKEN), an oops, a hang, data corruption, a real
> security issue, or some “oh, that’s not good” issue. In short,
> something critical.
>
> So this probably should be for net-next.
Okay, thanks! Just to spell it out this means you'll need to hold off
with reposting, Andy, until net-next re-opens (which means until
5.18-rc1 kernel version is tagged by Linus, see the netdev-FAQ).
You should also drop the Fixes tag from patch 4. The change will make
it to Linux 5.19 and won't be backported to stable.
next prev parent reply other threads:[~2022-03-30 1:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 2:49 [PATCH v7 net 0/4] Fix broken link on Xilinx's AXI Ethernet in SGMII mode Andy Chiu
2022-03-29 2:49 ` [PATCH v7 net 1/4] net: axienet: setup mdio unconditionally Andy Chiu
2022-03-29 2:49 ` [PATCH v7 net 2/4] net: axienet: factor out phy_node in struct axienet_local Andy Chiu
2022-03-29 2:49 ` [PATCH v7 net 3/4] dt-bindings: net: add pcs-handle attribute Andy Chiu
2022-04-04 18:08 ` Rob Herring
2022-03-29 2:49 ` [PATCH v7 net 4/4] net: axiemac: use a phandle to reference pcs_phy Andy Chiu
2022-03-29 22:56 ` Jakub Kicinski
2022-03-30 1:25 ` Andrew Lunn
2022-03-30 1:48 ` Jakub Kicinski [this message]
2022-03-30 8:50 ` Andy Chiu
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=20220329184819.6d4354b6@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=andy.chiu@sifive.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=greentime.hu@sifive.com \
--cc=linux@armlinux.org.uk \
--cc=michal.simek@xilinx.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=radhey.shyam.pandey@xilinx.com \
--cc=robert.hancock@calian.com \
--cc=robh+dt@kernel.org \
--cc=robh@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.