public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: "Petr Vaněk" <arkamar@atlas.cz>
Cc: fushuai.wang@linux.dev, andrew+netdev@lunn.ch,
	netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
	linux-kernel@vger.kernel.org, davem@davemloft.net,
	vadim.fedorenko@linux.dev, Jason@zx2c4.com,
	wireguard@lists.zx2c4.com, wangfushuai@baidu.com
Subject: Re: [net-next, v3] wireguard: allowedips: Use kfree_rcu() instead of call_rcu()
Date: Thu, 15 Jan 2026 06:26:41 -0800	[thread overview]
Message-ID: <20260115062641.57ef05fe@kernel.org> (raw)
In-Reply-To: <202611581213-aWihXdQpdnhXv606-arkamar@atlas.cz>

On Thu, 15 Jan 2026 09:12:13 +0100 Petr Vaněk wrote:
> Hi Jakub,
> 
> Minor side note: I noticed a small typo in the AI review foreword. I
> assume this is part of a template:
> 
> On Wed, Jan 14, 2026 at 07:32:37PM -0800, Jakub Kicinski wrote:
> > This is an AI-generated review of your patch. The human sending this
> > email has considered the AI review valid, or at least pausible.  
>                                                         ^~~~~~~~
> pausible -> plausible

Ah, thanks :)

      reply	other threads:[~2026-01-15 14:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-12 13:06 [PATCH net-next v3] wireguard: allowedips: Use kfree_rcu() instead of call_rcu() Fushuai Wang
2026-01-14 15:41 ` Simon Horman
2026-01-15  3:32 ` [net-next,v3] " Jakub Kicinski
2026-01-15  5:12   ` [PATCH net-next v3] " Fushuai Wang
2026-01-15  9:15     ` Eric Dumazet
2026-01-15 14:33       ` Jason A. Donenfeld
2026-01-15 14:40         ` Eric Dumazet
2026-01-22 23:30           ` Jason A. Donenfeld
2026-01-15  8:12   ` [net-next, " Petr Vaněk
2026-01-15 14:26     ` 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=20260115062641.57ef05fe@kernel.org \
    --to=kuba@kernel.org \
    --cc=Jason@zx2c4.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=arkamar@atlas.cz \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=fushuai.wang@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=vadim.fedorenko@linux.dev \
    --cc=wangfushuai@baidu.com \
    --cc=wireguard@lists.zx2c4.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