From: Jakub Kicinski <kuba@kernel.org>
To: Jason Xing <kerneljasonxing@gmail.com>
Cc: netdev@vger.kernel.org, netdev-driver-reviewers@vger.kernel.org,
andrew@lunn.ch, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, horms@kernel.org, johannes@sipsolutions.net,
kuni1840@gmail.com, willemb@google.com
Subject: Re: [ANN] netdev foundation
Date: Mon, 7 Jul 2025 10:40:41 -0700 [thread overview]
Message-ID: <20250707104041.17e26e4a@kernel.org> (raw)
In-Reply-To: <CAL+tcoBJmxE5+f8vZ=DbPRO=Bi84kEU=yrmqnuri30duva=HYg@mail.gmail.com>
On Thu, 3 Jul 2025 07:40:35 +0800 Jason Xing wrote:
> On Wed, Jul 2, 2025 at 11:08 PM Jakub Kicinski <kuba@kernel.org> wrote:
> > On Tue, 1 Jul 2025 10:31:49 -0700 Jakub Kicinski wrote:
> > > https://github.com/linux-netdev/foundation
> > >
> > > The README page provides more information about the scope, and
> > > the process. We don't want to repeat all that information - please
> > > refer to the README and feel free to comment or ask any questions here.
> > >
> > > And please feel free to suggest projects!
> >
> > I see a number of people opened the link (or maybe like most Internet
> > traffic these days it's just AI scraping bots? :D) but no project
> > proposals were added, yet.
>
> I hope I didn't misunderstand what you said here. I keep thinking if
> there are other projects related to kernel development.
Project in this context means something we can fund, for example adding
a specific feature to a specific tool, like patchwork.
prev parent reply other threads:[~2025-07-07 17:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 17:31 [ANN] netdev foundation Jakub Kicinski
2025-07-01 18:48 ` Simon Horman
2025-07-02 15:07 ` Jakub Kicinski
2025-07-02 23:40 ` Jason Xing
2025-07-07 17:40 ` Jakub Kicinski [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=20250707104041.17e26e4a@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=kerneljasonxing@gmail.com \
--cc=kuni1840@gmail.com \
--cc=netdev-driver-reviewers@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.