From: Jakub Kicinski <kuba@kernel.org>
To: Stefan Schmidt <stefan@datenfreihafen.org>
Cc: davem@davemloft.net, pabeni@redhat.com,
linux-wpan@vger.kernel.org, alex.aring@gmail.com,
miquel.raynal@bootlin.com, netdev@vger.kernel.org
Subject: Re: pull-request: ieee802154 for net 2023-03-24
Date: Tue, 28 Mar 2023 15:14:18 -0700 [thread overview]
Message-ID: <20230328151418.699f7026@kernel.org> (raw)
In-Reply-To: <605a1c16-0c03-a3be-9aec-12bb4d0113dc@datenfreihafen.org>
On Tue, 28 Mar 2023 09:10:07 +0200 Stefan Schmidt wrote:
> Sorry for that. I did not update my pull request script when changing
> the git tree URLs to our team tree. Updated now.
>
> The tag is now on the tree above. You want me to send a new pull request
> or do you take it from here?
Thanks, fresh PR would be better, I can't re-trigger the patchwork
checks on an existing one :(
next prev parent reply other threads:[~2023-03-28 22:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 17:39 pull-request: ieee802154 for net 2023-03-24 Stefan Schmidt
2023-03-28 2:38 ` Jakub Kicinski
2023-03-28 7:10 ` Stefan Schmidt
2023-03-28 22:14 ` Jakub Kicinski [this message]
2023-03-29 6:48 ` Stefan Schmidt
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=20230328151418.699f7026@kernel.org \
--to=kuba@kernel.org \
--cc=alex.aring@gmail.com \
--cc=davem@davemloft.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).