mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "jiale yao" <19888972804@163.com>
To: "Jakub Kicinski" <kuba@kernel.org>
Cc: "Willem de Bruijn" <willemdebruijn.kernel@gmail.com>,
	"Jason Wang" <jasowangio@gmail.com>,
	"Andrew Lunn" <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	"Eric Dumazet" <edumazet@google.com>,
	"Paolo Abeni" <pabeni@redhat.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re:Re: [PATCH 2/3] tun: Drain eBPF RCU callbacks on module exit
Date: Sat, 3 Oct 2026 17:45:04 +0800 (CST)	[thread overview]
Message-ID: <3283db82.138f.1a101272332.Coremail.19888972804@163.com> (raw)
In-Reply-To: <20261001161209.135f0aef@kernel.org>

Hi Jakub,
At 2026-10-02 07:12:09, "Jakub Kicinski" <kuba@kernel.org> wrote:
>On Sun, 27 Sep 2026 00:25:51 +0800 Jiale Yao wrote:
>> Subject: [PATCH 2/3] tun: Drain eBPF RCU callbacks on module exit
>
>please repost this if you expect networking to take the patch
>patchwork will wait for the other emails that you did not cc us on
>you shouldn't pointlessly make patches for different subsystems into 
>a series

Thanks for pointing this out. I have split out the TUN change and
reposted it as a standalone patch,
in https://lore.kernel.org/all/20261003093822.544964-1-yaojiale02@163.com/ 

Jiale

  reply	other threads:[~2026-10-03  9:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-26 16:25 [PATCH 0/3] Drain module-owned RCU callbacks during teardown Jiale Yao
2026-09-26 16:25 ` [PATCH 1/3] vfio/pci: Drain eventfd RCU callbacks on module exit Jiale Yao
2026-09-26 16:25 ` [PATCH 2/3] tun: Drain eBPF " Jiale Yao
2026-09-28 18:51   ` Willem de Bruijn
2026-10-01 23:12   ` Jakub Kicinski
2026-10-03  9:45     ` jiale yao [this message]
2026-09-26 16:25 ` [PATCH 3/3] drm/lima: Drain fence callbacks before destroying slab Jiale Yao

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=3283db82.138f.1a101272332.Coremail.19888972804@163.com \
    --to=19888972804@163.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jasowangio@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=willemdebruijn.kernel@gmail.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
all inboxes | Powered by JetHome®