From: Jakub Kicinski <kuba@kernel.org>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Alexander Aring <alex.aring@gmail.com>,
Stefan Schmidt <stefan@datenfreihafen.org>,
netdev@vger.kernel.org, linux-wpan@vger.kernel.org
Subject: Re: pull-request: ieee802154 for net-next 2023-12-20
Date: Thu, 4 Jan 2024 14:31:35 -0800 [thread overview]
Message-ID: <20240104143135.303e049f@kernel.org> (raw)
In-Reply-To: <20231222152017.729ee12b@xps-13>
On Fri, 22 Dec 2023 15:20:17 +0100 Miquel Raynal wrote:
> miquel.raynal@bootlin.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 :)
> 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@gitolite.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.
> https://patchwork.kernel.org/project/netdevbpf/patch/20231220095556.4d9cef91@xps-13/
>
> Let me know if there is anything wrong.
Pulled now, thanks!
next prev parent reply other threads:[~2024-01-04 22:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 8:55 pull-request: ieee802154 for net-next 2023-12-20 Miquel Raynal
2023-12-22 14:20 ` Miquel Raynal
2024-01-04 22:31 ` Jakub Kicinski [this message]
2024-01-08 7:28 ` Miquel Raynal
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=20240104143135.303e049f@kernel.org \
--to=kuba@kernel.org \
--cc=alex.aring@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-wpan@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stefan@datenfreihafen.org \
/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.