All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: azey <me@azey.net>
Cc: "David Ahern" <dsahern@kernel.org>,
	"nicolasdichtel" <nicolas.dichtel@6wind.com>,
	"David S. Miller" <davem@davemloft.net>,
	"Eric Dumazet" <edumazet@google.com>,
	"Paolo Abeni" <pabeni@redhat.com>,
	"Simon Horman" <horms@kernel.org>,
	"netdev" <netdev@vger.kernel.org>,
	"linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] net/ipv6: allow device-only routes via the multipath API
Date: Mon, 24 Nov 2025 19:25:50 -0800	[thread overview]
Message-ID: <20251124192550.09866129@kernel.org> (raw)
In-Reply-To: <19ab902473c.cef7bda2449598.3788324713972830782@azey.net>

On Tue, 25 Nov 2025 04:15:25 +0100 azey wrote:
> On 2025-11-25 04:00:44 +0100  Jakub Kicinski <kuba@kernel.org> wrote:
> > On Mon, 24 Nov 2025 14:52:45 +0100 azey wrote:  
> > > Signed-off-by: azey <me@azey.net>  
> > 
> > We need real/legal names because licenses are a legal matter.
> > -- 
> > pw-bot: cr  
> 
> I was under the impression this was clarified in d4563201f33a
> ("Documentation: simplify and clarify DCO contribution example
> language") to not be the case, are there different rules for this
> subsystem? I think it qualifies as a "known identity" since I use
> the alias basically everywhere (github, website, GPG, email, etc).

My understanding is that if I know you, I can apply your patch even 
if you use your nick name (rather than what you have in your passport
letter for letter).

I don't know you.

If you're saying that I can do some research and find out who you are
please be aware that we deal with 700 individual per release just
in networking.

  reply	other threads:[~2025-11-25  3:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-24 13:52 [PATCH v2] net/ipv6: allow device-only routes via the multipath API azey
2025-11-25  3:00 ` Jakub Kicinski
2025-11-25  3:15   ` azey
2025-11-25  3:25     ` Jakub Kicinski [this message]
2025-11-25  4:00       ` azey
2025-11-25  4:20         ` Jakub Kicinski
2025-11-25  5:30           ` azey
2025-11-26 17:51   ` azey
2025-11-27  7:58     ` Nicolas Dichtel
2025-11-27 14:06       ` azey
2025-11-28  8:38         ` Nicolas Dichtel
2025-11-28 12:38           ` azey
2025-11-28 13:22             ` azey
2025-11-28 15:28             ` Nicolas Dichtel
2025-11-28 15:45               ` azey
2025-11-28 15:54                 ` azey
2025-11-28 16:28                   ` Nicolas Dichtel
2025-11-28 17:49                     ` azey
2025-12-01 15:38                       ` Nicolas Dichtel

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=20251124192550.09866129@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=me@azey.net \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.dichtel@6wind.com \
    --cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.