From: Jakub Kicinski <kuba@kernel.org>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: davem@davemloft.net, pabeni@redhat.com, alex.aring@gmail.com,
stefan@datenfreihafen.org, netdev@vger.kernel.org,
linux-wpan@vger.kernel.org
Subject: Re: pull-request: ieee802154 for net-next 2023-06-23
Date: Sat, 24 Jun 2023 15:59:47 -0700 [thread overview]
Message-ID: <20230624155947.1b94903e@kernel.org> (raw)
In-Reply-To: <20230623195506.40b87b5f@xps-13>
On Fri, 23 Jun 2023 19:55:06 +0200 Miquel Raynal wrote:
> As you know, we are trying to build a wpan maintainers group so here is
> my first ieee802154 pull-request for your *net-next* tree.
Pulled thanks!
In the future, please try to avoid merging in tags from Linus's tree
directly. You can send a PR to net-next and fast forward, that results
in a more straightforward shape of the history, and avoids getting
the back-merging wrong (Linus said a couple of times that any cross-
-merge must have an explanation in the commit message, for example).
next prev parent reply other threads:[~2023-06-24 22:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 17:55 pull-request: ieee802154 for net-next 2023-06-23 Miquel Raynal
2023-06-24 22:59 ` Jakub Kicinski [this message]
2023-06-26 10:39 ` 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=20230624155947.1b94903e@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).