From: Jakub Kicinski <kuba@kernel.org>
To: linux-hams@vger.kernel.org
Cc: Chris Maness <christopher.maness@gmail.com>,
hugh@blemings.id.au, Greg KH <gregkh@linuxfoundation.org>,
Kuniyuki Iwashima <kuniyu@google.com>,
davem@davemloft.net, edumazet@google.com, horms@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, stable@kernel.org, workflows@vger.kernel.org,
yizhe@darknavy.com, f6bvp <bernard.f6bvp@gmail.com>,
Jean-Paul Roubelat <jpr@f6fbb.org>,
Joerg Reuter <jreuter@yaina.de>,
Andreas Koensgen <ajk@comnets.uni-bremen.de>,
Thomas Sailer <t.sailer@alumni.ethz.ch>
Subject: Re: [PATCH net] netrom: do some basic forms of validation on incoming frames
Date: Thu, 16 Apr 2026 09:58:44 -0700 [thread overview]
Message-ID: <20260416095844.12f628fa@kernel.org> (raw)
In-Reply-To: <CANnsUMFVg9nZnJ_He38O9Ui1YUM_Je7MGO-y_J+oW=TG3jV1bA@mail.gmail.com>
On Sun, 12 Apr 2026 05:56:50 -0700 Chris Maness wrote:
> Thanks for your work, Hugh.
Hi good folks of hamradio.
There was a blip of activity after this thread started but now core
networking maintainers are back to reviewing all the fixes themselves
again.
We would like y'all to set up a git tree so that you can handle all the
incoming AI patches, and send them out as a pull request. This is how
wifi, bluetooth etc. operate. You already have a mailing list so that's
good.
We do not have the capacity to review all the AI generated fixes, and
ignoring security fixes does not feel like an option. I'm planning to
send a PR early next week, shedding some low usage / high CVE count code
I hope you can have the tree in place by then.
prev parent reply other threads:[~2026-04-16 16:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 8:45 [PATCH net] netrom: do some basic forms of validation on incoming frames Greg Kroah-Hartman
2026-04-09 19:03 ` Simon Horman
2026-04-10 3:32 ` Jakub Kicinski
2026-04-10 5:24 ` Greg Kroah-Hartman
2026-04-10 10:28 ` Simon Horman
2026-04-10 15:12 ` jj
2026-04-10 16:38 ` David Ranch
2026-04-10 17:21 ` Dan Carpenter
2026-04-10 18:23 ` Dan Cross
2026-04-10 21:30 ` Jakub Kicinski
2026-04-10 21:54 ` Jakub Kicinski
2026-04-10 22:11 ` Kuniyuki Iwashima
2026-04-10 22:25 ` Hugh Blemings
2026-04-10 22:51 ` Craig
2026-04-10 23:38 ` Hugh Blemings
[not found] ` <CANnsUMEniMzLnp5h=Gz83=Wcegc-jGz9vqyWyEpWx-OH=Dij1w@mail.gmail.com>
2026-04-11 20:33 ` Chris Maness
2026-04-12 14:41 ` Jakub Kicinski
2026-04-11 5:50 ` Greg KH
2026-04-11 7:24 ` Hugh Blemings
2026-04-11 8:58 ` Greg KH
2026-04-12 2:32 ` Hugh Blemings
2026-04-12 12:56 ` Chris Maness
2026-04-16 16:58 ` 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=20260416095844.12f628fa@kernel.org \
--to=kuba@kernel.org \
--cc=ajk@comnets.uni-bremen.de \
--cc=bernard.f6bvp@gmail.com \
--cc=christopher.maness@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=horms@kernel.org \
--cc=hugh@blemings.id.au \
--cc=jpr@f6fbb.org \
--cc=jreuter@yaina.de \
--cc=kuniyu@google.com \
--cc=linux-hams@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@kernel.org \
--cc=t.sailer@alumni.ethz.ch \
--cc=workflows@vger.kernel.org \
--cc=yizhe@darknavy.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