From: Jacob Keller <jacob.e.keller@intel.com>
To: Birger Koblitz <mail@birger-koblitz.de>,
Paul Menzel <pmenzel@molgen.mpg.de>, Andrew Lunn <andrew@lunn.ch>
Cc: Tony Nguyen <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
<intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [Intel-wired-lan] [PATCH net-next v2] ixgbe: Add 10G-BX support
Date: Tue, 14 Oct 2025 16:36:58 -0700 [thread overview]
Message-ID: <0db6777d-1f2e-438c-b56c-9af16787dd27@intel.com> (raw)
In-Reply-To: <4fcabfb2-9793-49be-bf60-bb8ac36f9e34@birger-koblitz.de>
[-- Attachment #1.1: Type: text/plain, Size: 516 bytes --]
On 10/14/2025 6:22 AM, Birger Koblitz wrote:
>
>
> On 14/10/2025 15:07, Paul Menzel wrote:
>> Unfortunately I do not see the original patch on the mailing list *intel-wired-lan*, and lore.kernel.org also does not have it [1].
>>
> I have several emails from intel-wired-lan stating that "Your message to Intel-wired-lan awaits moderator approval" as I am not myself on that list.
>
> Birger
>
I approved the messages. They should make it through to the list and
archives soon.
Thanks,
Jake
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2025-10-14 23:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 4:18 [PATCH net-next v2] ixgbe: Add 10G-BX support Birger Koblitz
2025-10-14 12:27 ` Andrew Lunn
2025-10-14 13:07 ` [Intel-wired-lan] " Paul Menzel
2025-10-14 13:22 ` Birger Koblitz
2025-10-14 23:36 ` Jacob Keller [this message]
2025-10-15 7:59 ` Paul Menzel
2025-10-15 9:16 ` Birger Koblitz
2025-10-15 9:38 ` Paul Menzel
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=0db6777d-1f2e-438c-b56c-9af16787dd27@intel.com \
--to=jacob.e.keller@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@birger-koblitz.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pmenzel@molgen.mpg.de \
--cc=przemyslaw.kitszel@intel.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;
as well as URLs for NNTP newsgroup(s).