public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>,
	 Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: Willem de Bruijn <willemb@google.com>,
	 "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [TEST] txtimestamp.sh pains after netdev foundation migration
Date: Mon, 12 Jan 2026 11:38:55 -0500	[thread overview]
Message-ID: <willemdebruijn.kernel.1ebfc524172ab@gmail.com> (raw)
In-Reply-To: <20260112062934.6d1b60c5@kernel.org>

Jakub Kicinski wrote:
> On Sun, 11 Jan 2026 22:28:39 -0500 Willem de Bruijn wrote:
> > > Can fold in the record_timestamp_usr() change too.
> > > 
> > > I can send this, your alternative with Suggested-by, or let me know if
> > > you prefer to send that.
> 
> Looks like we got 30 clean runs since I added the printing change 
> to the local NIPA hacks.

Wow nice.

> Let's start with that and see if it's good
> enough? As trivial as the change is I have the feeling that is has
> to be something trivial for us to fail 30% of the attempts.
> 
> Please go ahead and submit with my Suggested-by.

https://lore.kernel.org/netdev/20260112163355.3510150-1-willemdebruijn.kernel@gmail.com/T/#u

      reply	other threads:[~2026-01-12 16:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-07 19:05 [TEST] txtimestamp.sh pains after netdev foundation migration Jakub Kicinski
2026-01-08  0:19 ` Willem de Bruijn
2026-01-08  3:25   ` Jakub Kicinski
2026-01-08 16:06     ` Jakub Kicinski
2026-01-08 19:02       ` Willem de Bruijn
2026-01-08 20:38         ` Jakub Kicinski
2026-01-08 21:19           ` Willem de Bruijn
2026-01-12  3:24             ` Willem de Bruijn
2026-01-12  3:28               ` Willem de Bruijn
2026-01-12 14:29                 ` Jakub Kicinski
2026-01-12 16:38                   ` Willem de Bruijn [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=willemdebruijn.kernel.1ebfc524172ab@gmail.com \
    --to=willemdebruijn.kernel@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox