public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel•org>
To: "Jason A. Donenfeld" <Jason@zx2c4•com>
Cc: Shardul Bankar <shardul.b@mpiricsoftware•com>,
	kuniyu@google•com, andrew+netdev@lunn•ch, davem@davemloft•net,
	edumazet@google•com, pabeni@redhat•com,
	wireguard@lists•zx2c4.com, netdev@vger•kernel.org,
	linux-kernel@vger•kernel.org, janak@mpiric•us,
	kalpan.jani@mpiricsoftware•com, shardulsb08@gmail•com,
	syzbot+f2fbf7478a35a94c8b7c@syzkaller•appspotmail.com
Subject: Re: [PATCH v2] wireguard: device: use exit_rtnl callback instead of manual rtnl_lock in pre_exit
Date: Tue, 14 Apr 2026 08:44:06 -0700	[thread overview]
Message-ID: <20260414084406.779336af@kernel.org> (raw)
In-Reply-To: <CAHmME9rwKae5b9PYzuqmwG3p05iZ=jqyp6LQefg0OsB3OP6oWg@mail.gmail.com>

On Tue, 14 Apr 2026 17:40:03 +0200 Jason A. Donenfeld wrote:
> On Tue, Apr 14, 2026 at 5:18 PM Jakub Kicinski <kuba@kernel•org> wrote:
> >
> > On Tue, 14 Apr 2026 15:28:37 +0200 Jason A. Donenfeld wrote:  
> > > Thanks. Applied to the wireguard tree, and also added the missing
> > > __net_exit and __read_mostly annotations in the process.  
> >
> > Hi Jason, while we have you - do you have a PR for us for wireguard?
> > We're going to be sending the net-next PR later today..  
> 
> Sent!

Thanks! 
(I'll apply in a couple of hours once the CI had its way with it.)

      reply	other threads:[~2026-04-14 15:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-13 15:12 [PATCH v2] wireguard: device: use exit_rtnl callback instead of manual rtnl_lock in pre_exit Shardul Bankar
2026-04-14 13:28 ` Jason A. Donenfeld
2026-04-14 15:18   ` Jakub Kicinski
2026-04-14 15:40     ` Jason A. Donenfeld
2026-04-14 15:44       ` Jakub Kicinski [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=20260414084406.779336af@kernel.org \
    --to=kuba@kernel$(echo .)org \
    --cc=Jason@zx2c4$(echo .)com \
    --cc=andrew+netdev@lunn$(echo .)ch \
    --cc=davem@davemloft$(echo .)net \
    --cc=edumazet@google$(echo .)com \
    --cc=janak@mpiric$(echo .)us \
    --cc=kalpan.jani@mpiricsoftware$(echo .)com \
    --cc=kuniyu@google$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    --cc=shardul.b@mpiricsoftware$(echo .)com \
    --cc=shardulsb08@gmail$(echo .)com \
    --cc=syzbot+f2fbf7478a35a94c8b7c@syzkaller$(echo .)appspotmail.com \
    --cc=wireguard@lists$(echo .)zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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