From: Jakub Kicinski <kuba@kernel.org>
To: Marc Sune <marcdevel@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next v4 2/4] selftests/net: add no ARP b/mcast,null poison test
Date: Wed, 11 Feb 2026 10:49:19 -0800 [thread overview]
Message-ID: <20260211104919.2c455de9@kernel.org> (raw)
In-Reply-To: <CA+3n-TpV8pg9exk15vGpPX3OW1-k-pLSiixUZ2UEvbFOgcc0+g@mail.gmail.com>
On Wed, 11 Feb 2026 19:29:01 +0100 Marc Sune wrote:
> > The word "poison" is misspelled but both in the file name and makefile.
> > I guess there's another typo somewhere.
>
> Sigh. Let me fix that, along with your comment on patch 4
> (TEST_GEN_FILES vs. _PROGS) on the other thread. I will also fix some
> AI review warnings (error traces) on patch 4 that AI reviews _now_
> highlighted. It seems AI reviews are non deterministic, as
> ndisc_send.c didn't change since v2, and the patch didn't even change
> v3->v4.
>
> I guess you'd like me to wait till net-next is open again, correct?
Yes, let's wait for net-next.
next prev parent reply other threads:[~2026-02-11 18:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-07 20:40 [PATCH net-next v4 0/4] discard ARP/NDP b/mcast/null announce (poison) Marc Suñé
2026-02-07 20:40 ` [PATCH net-next v4 1/4] arp: discard invalid sha addr (b/mcast ARP poison) Marc Suñé
2026-02-07 20:40 ` [PATCH net-next v4 2/4] selftests/net: add no ARP b/mcast,null poison test Marc Suñé
2026-02-11 2:11 ` Jakub Kicinski
2026-02-11 18:29 ` Marc Sune
2026-02-11 18:49 ` Jakub Kicinski [this message]
2026-02-07 20:40 ` [PATCH net-next v4 3/4] neigh: discard invalid lladdr (b/mcast poison) Marc Suñé
2026-02-07 20:40 ` [PATCH net-next v4 4/4] selftests/net: add no NDP b/mcast,null poison test Marc Suñé
2026-02-11 2:11 ` Jakub Kicinski
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=20260211104919.2c455de9@kernel.org \
--to=kuba@kernel.org \
--cc=marcdevel@gmail.com \
--cc=netdev@vger.kernel.org \
/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.