public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Pavel Begunkov <asml.silence@gmail.com>,
	io-uring@vger.kernel.org,
	Vadim Fedorenko <vadim.fedorenko@linux.dev>,
	netdev@vger.kernel.org, Eric Dumazet <edumazet@google.com>,
	Kuniyuki Iwashima <kuniyu@amazon.com>,
	Paolo Abeni <pabeni@redhat.com>,
	Willem de Bruijn <willemb@google.com>,
	"David S . Miller" <davem@davemloft.net>,
	Richard Cochran <richardcochran@gmail.com>,
	Stanislav Fomichev <sdf@fomichev.me>,
	Jason Xing <kerneljasonxing@gmail.com>
Subject: Re: [PATCH v5 0/5] io_uring cmd for tx timestamps
Date: Tue, 17 Jun 2025 15:41:03 -0700	[thread overview]
Message-ID: <20250617154103.519b5b9d@kernel.org> (raw)
In-Reply-To: <520fa72f-1105-42f6-a16f-050873be8742@kernel.dk>

On Tue, 17 Jun 2025 16:33:20 -0600 Jens Axboe wrote:
> >> Sounds like we're good to queue this up for 6.17?  
> > 
> > I think so. Can I apply patch 1 off v6.16-rc1 and merge it in to
> > net-next? Hash will be 2410251cde0bac9f6, you can pull that across.
> > LMK if that works.  
> 
> Can we put it in a separate branch and merge it into both? Otherwise
> my branch will get a bunch of unrelated commits, and pulling an
> unnamed sha is pretty iffy.

Like this?

 https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git timestamp-for-jens

  reply	other threads:[~2025-06-17 22:41 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-16  9:46 [PATCH v5 0/5] io_uring cmd for tx timestamps Pavel Begunkov
2025-06-16  9:46 ` [PATCH v5 1/5] net: timestamp: add helper returning skb's tx tstamp Pavel Begunkov
2025-06-16 14:53   ` Willem de Bruijn
2025-06-16 15:01   ` Willem de Bruijn
2025-06-16 16:37     ` Pavel Begunkov
2025-06-16 16:43       ` Willem de Bruijn
2025-06-17 16:30     ` Willem de Bruijn
2025-06-18  7:01   ` Jason Xing
2025-06-16  9:46 ` [PATCH v5 2/5] io_uring/poll: introduce io_arm_apoll() Pavel Begunkov
2025-06-16  9:46 ` [PATCH v5 3/5] io_uring/cmd: allow multishot polled commands Pavel Begunkov
2025-06-16  9:46 ` [PATCH v5 4/5] io_uring: add mshot helper for posting CQE32 Pavel Begunkov
2025-06-16  9:46 ` [PATCH v5 5/5] io_uring/netcmd: add tx timestamping cmd support Pavel Begunkov
2025-06-17 14:52 ` [PATCH v5 0/5] io_uring cmd for tx timestamps Jens Axboe
2025-06-17 22:29   ` Jakub Kicinski
2025-06-17 22:33     ` Jens Axboe
2025-06-17 22:41       ` Jakub Kicinski [this message]
2025-06-17 22:41         ` Jens Axboe
2025-06-20 14:31         ` Jens Axboe
2025-06-20 16:30           ` Pavel Begunkov
2025-06-20 19:46           ` Jakub Kicinski
2025-06-21  0:45             ` Jens Axboe
2025-06-23 15:00             ` Jens Axboe
2025-06-23 15:01 ` (subset) " Jens Axboe
2025-06-27 17:07   ` Jens Axboe
2025-06-28  6:10     ` Pavel Begunkov
2025-07-08 17:55       ` Jens Axboe
2025-07-08 18:00         ` Pavel Begunkov
2025-07-08 18:00           ` Jens Axboe

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=20250617154103.519b5b9d@kernel.org \
    --to=kuba@kernel.org \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=io-uring@vger.kernel.org \
    --cc=kerneljasonxing@gmail.com \
    --cc=kuniyu@amazon.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=richardcochran@gmail.com \
    --cc=sdf@fomichev.me \
    --cc=vadim.fedorenko@linux.dev \
    --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