From: Andrew Lunn <andrew@lunn.ch>
To: Andrei Botila <andrei.botila@oss.nxp.com>
Cc: Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
s32@nxp.com, Christophe Lizzi <clizzi@redhat.com>,
Alberto Ruiz <aruizrui@redhat.com>,
Enric Balletbo <eballetb@redhat.com>
Subject: Re: [PATCH 0/3] net: phy: nxp-c45-tja11xx: add support for TJA1121 and errata
Date: Thu, 27 Feb 2025 17:58:37 +0100 [thread overview]
Message-ID: <c0537f48-ed07-4afd-acf8-4d858ffa72e9@lunn.ch> (raw)
In-Reply-To: <7f737895-339e-4a0a-abb4-cec8a61ba3b8@oss.nxp.com>
On Thu, Feb 27, 2025 at 06:33:31PM +0200, Andrei Botila wrote:
> On 2/27/2025 6:11 PM, Andrew Lunn wrote:
> > On Thu, Feb 27, 2025 at 06:00:53PM +0200, Andrei Botila wrote:
> > > This patch series adds support for TJA1121 and two errata for latest
> > > silicon version of TJA1120 and TJA1121.
> >
> > Should the errata fixes be back ported to stable for the TJA1120? If
> > so, you need to base them on net, and include a Fixes: tag. Adding the
> > new device is however net-next material.
>
> The errata fixes don't have to be ported to stable.
An explanation why would be nice.
Andrew
prev parent reply other threads:[~2025-02-27 16:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 16:00 Andrei Botila
2025-02-27 16:00 ` [PATCH 1/3] net: phy: nxp-c45-tja11xx: add support for TJA1121 Andrei Botila
2025-02-27 16:14 ` Andrew Lunn
2025-02-27 16:30 ` Andrei Botila
2025-02-27 16:56 ` Andrew Lunn
2025-02-27 16:00 ` [PATCH 2/3] net: phy: nxp-c45-tja11xx: add TJA112X PHY configuration errata Andrei Botila
2025-02-27 16:00 ` [PATCH 3/3] net: phy: nxp-c45-tja11xx: add TJA112XB SGMII PCS restart errata Andrei Botila
2025-02-27 16:11 ` [PATCH 0/3] net: phy: nxp-c45-tja11xx: add support for TJA1121 and errata Andrew Lunn
2025-02-27 16:33 ` Andrei Botila
2025-02-27 16:58 ` Andrew Lunn [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=c0537f48-ed07-4afd-acf8-4d858ffa72e9@lunn.ch \
--to=andrew@lunn.ch \
--cc=andrei.botila@oss.nxp.com \
--cc=aruizrui@redhat.com \
--cc=clizzi@redhat.com \
--cc=davem@davemloft.net \
--cc=eballetb@redhat.com \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=s32@nxp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®