netdev - Re: pull-request: ieee802154 for net-next 2023-12-20

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date: Mon, 8 Jan 2024 08:28:37 +0100
From: Miquel Raynal <miquel.raynal@...tlin.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: "David S. Miller" <davem@...emloft.net>, Eric Dumazet
 <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>, Alexander Aring
 <alex.aring@...il.com>, Stefan Schmidt <stefan@...enfreihafen.org>,
 netdev@...r.kernel.org, linux-wpan@...r.kernel.org
Subject: Re: pull-request: ieee802154 for net-next 2023-12-20

Hi Jakub,

kuba@...nel.org wrote on Thu, 4 Jan 2024 14:31:35 -0800:

> On Fri, 22 Dec 2023 15:20:17 +0100 Miquel Raynal wrote:
> > miquel.raynal@...tlin.com wrote on Wed, 20 Dec 2023 09:55:56 +0100:
> >   
> > > Hello Dave, Jakub, Paolo, Eric.
> > > 
> > > This is the ieee802154 pull-request for your *net-next* tree.    
> > 
> > I'm sorry for doing this but I saw the e-mail saying net-next would
> > close tomorrow, I'd like to ensure you received this PR, as you
> > are usually quite fast at merging them and the deadline approaches.  
> 
> Sorry for the delay, I only caught up with enough email now :)

No problem with the delay, sometimes e-mails get lost in SPAM folders
and I was unsure about whether you would pull after closing (and
possibly re-opening) ne-next.

> > It appears on patchwork, but the "netdev apply" worker failed, I've no
> > idea why, rebasing on net-next does not show any issue.  
> 
> That's because the pull URL is:
> 
> git@...olite.kernel.org:pub ...
> 
> the bot doesn't have SSH access to kernel.org. IIRC you need to set 
> the fetch URL in git remote for your repo to be over HTTPS. Only
> leave push over SSH.

Oh, right, indeed on another repo used to generate pull requests I have
a different fetch/push remote, but I totally overlooked that one. I will
update my setup, thanks for the tip!

> > https://patchwork.kernel.org/project/netdevbpf/patch/20231220095556.4d9cef91@xps-13/
> > 
> > Let me know if there is anything wrong.  
> 
> Pulled now, thanks!

Perfect, thanks!

Miquèl