From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Patryk Biel <pbiel7@gmail.com>
Cc: Ioana Ciornei <ioana.ciornei@nxp.com>,
Andrew Lunn <andrew@lunn.ch>,
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
Subject: Re: [PATCH] net: pcs: enable autonegotiation for 10g-usxgmii
Date: Wed, 26 Aug 2026 23:19:52 +0300 [thread overview]
Message-ID: <20260826201952.pmvweuqb3awr7vay@skbuf> (raw)
In-Reply-To: <CA+DkFDZzFLHxgBv5Z260gwk4UbYAONxtTewFHPV2vV2M6z0Q+g@mail.gmail.com>
On Mon, Aug 24, 2026 at 02:54:54PM +0200, Patryk Biel wrote:
> Hi,
> pt., 21 sie 2026 o 12:00 Ioana Ciornei <ioana.ciornei@nxp.com> napisał(a):
>
> > For v2 please explicitly target the net tree by changing the subject
> > prefix to "PATCH net ".
>
> Applied all requested changes, however, according to this suggestion
> ("PATCH net") I also rebased my changes and changed target to net
> instead of net-next, and I now see that on patchwork one check is
> failing, namely "netdev/fixes_present". May I ask how I should proceed
> with this - should I add a Fixes tag, or change the base back to
> net-next?
>
> Best regards
> Patryk
I discussed this with Ioana, and we now think it would be better to
retarget v3 for net-next, given:
- the fact that you are effectively removing a bootloader dependency
(which can be seen as further developing the driver), not fixing a
breakage (which will be backported to stable kernels)
- the risk for introducing regressions in said stable kernels
But yes, patches targeted for 'net' should have a Fixes: tag.
prev parent reply other threads:[~2026-08-26 20:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 17:41 [PATCH] net: pcs: enable autonegotiation for 10g-usxgmii Patryk Biel
2026-08-20 18:24 ` Andrew Lunn
2026-08-21 10:00 ` Ioana Ciornei
2026-08-24 12:54 ` Patryk Biel
2026-08-26 20:19 ` Vladimir Oltean [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=20260826201952.pmvweuqb3awr7vay@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=ioana.ciornei@nxp.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=pbiel7@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox