From: Jakub Kicinski <kuba@kernel.org>
To: Daniel Wagner <wagner.daniel.t@gmail.com>
Cc: netdev@vger.kernel.org,
Florian Fainelli <florian.fainelli@broadcom.com>,
Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
bcm-kernel-feedback-list@broadcom.com,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net-next v2] net: phy: bcm84881: add BCM84891/BCM84892 support
Date: Mon, 30 Mar 2026 15:39:20 -0700 [thread overview]
Message-ID: <20260330153920.04e62663@kernel.org> (raw)
In-Reply-To: <CAMsLQxGcnD1Q8REcgKWJQR-cgS2Z1KaTJgs9r989p2pxz6vV4Q@mail.gmail.com>
On Sun, 29 Mar 2026 17:47:47 +0100 Daniel Wagner wrote:
> I see v2 is marked as "changes requested" on patchwork; I believe it
> addresses the original points, but happy to make further changes if I
> missed something. LEDs will follow in a separate patch.
Repost it, say in the change log that it's identical to v2.
You posted this while the discussion was still ongoing which
is an automatic expulsion from patchwork.
next prev parent reply other threads:[~2026-03-30 22:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 15:25 [PATCH net-next] net: phy: bcm84881: add BCM84891/BCM84892 support Daniel Wagner
2026-03-24 15:49 ` Russell King (Oracle)
2026-03-24 18:54 ` Daniel Wagner
2026-03-24 19:18 ` Andrew Lunn
2026-03-24 19:42 ` Daniel Wagner
2026-03-24 20:01 ` Russell King (Oracle)
2026-03-24 21:59 ` Daniel Wagner
2026-03-24 22:53 ` Russell King (Oracle)
2026-03-24 19:32 ` Russell King (Oracle)
2026-03-24 15:52 ` Andrew Lunn
2026-03-24 19:06 ` [PATCH net-next v2] " Daniel Wagner
2026-03-29 16:47 ` Daniel Wagner
2026-03-30 22:39 ` Jakub Kicinski [this message]
2026-03-30 22:01 ` Florian Fainelli
2026-03-30 22:44 ` Nicolai Buchwitz
2026-03-30 23:34 ` Russell King (Oracle)
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=20260330153920.04e62663@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=hkallweit1@gmail.com \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wagner.daniel.t@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