From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Patryk Biel <pbiel7@gmail.com>
Cc: Vladimir Oltean <olteanv@gmail.com>,
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 v2] net: pcs: enable autonegotiation for 10g-usxgmii
Date: Thu, 27 Aug 2026 12:18:43 +0300 [thread overview]
Message-ID: <20260827091843.ciajpqeh32ikqe3b@skbuf> (raw)
In-Reply-To: <CA+DkFDZLv5BS7z7MEV_uBFdNgfrBQr_nkzGa2q6BKx_F4fU0xQ@mail.gmail.com>
On Thu, Aug 27, 2026 at 10:59:40AM +0200, Patryk Biel wrote:
> I tested it and it keeps working fine. Logs below, but there is
> nothing new compared to the previous test.
That's great news.
I've started a discussion internally, hoping to get a confirmation from
the design team that our documentation is indeed wrong.
> Given your other email, for v3, I understand that I should retarget
> the patch from net to net-next.
Yeah.
> I'm just not sure how you'd prefer to handle your changes. Should I
> fold them into my patch for v3, or are you planning to send them
> separately?
No, why would we introduce a bug only to fix it later? The AQR412C
systems must continue to work, so you'd have to fold my change into
yours. Per Documentation/process/submitting-patches.rst, you may use
Co-developed-by: and Signed-off-by: to also credit me for that part of
the change, if you wish.
But note that net-next is currently closed due to the merge window.
https://lore.kernel.org/netdev/20260816155953.072d73da@kernel.org/
next prev parent reply other threads:[~2026-08-27 9:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 10:36 [PATCH net v2] net: pcs: enable autonegotiation for 10g-usxgmii Patryk Biel
2026-08-25 21:49 ` Vladimir Oltean
2026-08-26 7:37 ` Patryk Biel
2026-08-26 15:36 ` Vladimir Oltean
2026-08-27 8:59 ` Patryk Biel
2026-08-27 9:18 ` Vladimir Oltean [this message]
2026-08-27 8:55 ` Vladimir Oltean
2026-08-27 9:13 ` Patryk Biel
2026-08-27 9:48 ` Vladimir Oltean
2026-08-27 10:18 ` Patryk Biel
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=20260827091843.ciajpqeh32ikqe3b@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=olteanv@gmail.com \
--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