[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240129-astute-winged-barnacle-eeffad@lemur>
Date: Mon, 29 Jan 2024 12:45:24 -0500
From: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
To: Arınç ÜNAL <arinc.unal@...nc9.com>
Cc: Linus Walleij <linus.walleij@...aro.org>,
Vladimir Oltean <olteanv@...il.com>, Luiz Angelo Daros de Luca <luizluca@...il.com>,
netdev@...r.kernel.org, alsi@...g-olufsen.dk, andrew@...n.ch, f.fainelli@...il.com,
davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com
Subject: Re: [PATCH net-next v3 0/8] net: dsa: realtek: variants to drivers,
interfaces to a common module
On Sun, Jan 21, 2024 at 01:13:36AM +0300, Arınç ÜNAL wrote:
> I've had trouble with every mail provider's SMTP server that I've ever used
> for submitting patches, so the web endpoint is a godsend. It would've been
> great if b4 supported openssh keys to submit patches via the web endpoint.
The only reason it's not currently supported is because we don't have a recent
enough version of openssh on the system where the endpoint is listening. This
will change in the near future, at which point using ssh keys will be
possible.
> Patatt at least supports it to sign patches. I've got a single ed25519
> openssh keypair I use across all my devices, now I'll have to backup
> another key pair. Or create a new key and authenticate with the web
> endpoint on each device.
>
> Safe to say, I will submit my next patch series using b4. Thanks for
> telling me about this tool Linus!
\o/
Please feel free to provide any feedback you have to the tools@...nel.org
list.
-K
Powered by blists - more mailing lists