From: Breno Leitao <leitao@debian.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Fernando Fernandez Mancera <fmancera@suse.de>,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
horms@kernel.org, pabeni@redhat.com, edumazet@google.com,
dsahern@kernel.org, davem@davemloft.net
Subject: Re: [PATCH 2/2 net v4] selftests: fib_tests: add temporary IPv6 address renewal test
Date: Wed, 13 May 2026 01:42:53 -0700 [thread overview]
Message-ID: <agQ5e5sSzKTU_L4h@gmail.com> (raw)
In-Reply-To: <20260512165641.1f557ba8@kernel.org>
On Tue, May 12, 2026 at 04:56:41PM -0700, Jakub Kicinski wrote:
> On Tue, 12 May 2026 01:08:15 -0700 Breno Leitao wrote:
> > On Mon, May 11, 2026 at 05:08:48PM -0700, Jakub Kicinski wrote:
> > > On Mon, 11 May 2026 10:01:00 -0700 Breno Leitao wrote:
> > > > Should you check for ra6 before the "setup" above?
> > >
> > > Not really. AI bots love to complain about this. But "ra6 command
> > > not found" is as good of a message as the explicit skip, honestly.
> >
> > Right, but why call setup() before checking if ra6 is available?
>
> You cut off the sentence from my response which told you why.
>
> Checking dependencies is not a priority for our tests.
Ack. Notes taken, sorry for the noise,
--breno
next prev parent reply other threads:[~2026-05-13 8:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 12:26 [PATCH 1/2 net v4] ipv6: addrconf: fix temp address generation after prefix deprecation Fernando Fernandez Mancera
2026-05-11 12:26 ` [PATCH 2/2 net v4] selftests: fib_tests: add temporary IPv6 address renewal test Fernando Fernandez Mancera
2026-05-11 17:01 ` Breno Leitao
2026-05-12 0:08 ` Jakub Kicinski
2026-05-12 8:08 ` Breno Leitao
2026-05-12 23:56 ` Jakub Kicinski
2026-05-13 8:42 ` Breno Leitao [this message]
2026-05-12 18:24 ` [PATCH 1/2 net v4] ipv6: addrconf: fix temp address generation after prefix deprecation Fernando Fernandez Mancera
2026-05-13 14:35 ` Ido Schimmel
2026-05-13 0:01 ` Jakub Kicinski
2026-05-13 7:17 ` Ido Schimmel
2026-05-13 7:48 ` Fernando Fernandez Mancera
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=agQ5e5sSzKTU_L4h@gmail.com \
--to=leitao@debian.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=fmancera@suse.de \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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