* pull-request: ieee802154 for net-next 2023-06-23
@ 2023-06-23 17:55 Miquel Raynal
2023-06-24 22:59 ` Jakub Kicinski
0 siblings, 1 reply; 3+ messages in thread
From: Miquel Raynal @ 2023-06-23 17:55 UTC (permalink / raw)
To: davem, kuba, pabeni; +Cc: alex.aring, stefan, netdev, linux-wpan
Hello Dave, Jakub, Paolo.
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.
Thanks,
Miquèl
The following changes since commit 7877cb91f1081754a1487c144d85dc0d2e2e7fc4:
Linux 6.4-rc4 (2023-05-28 07:49:00 -0400)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/wpan/wpan-next.git tags/ieee802154-for-net-next-2023-06-23
for you to fetch changes up to 18b849f12dcc34ec4cb9c8fadeb503b069499ba4:
ieee802154: ca8210: Remove stray gpiod_unexport() call (2023-06-06 20:47:48 +0200)
----------------------------------------------------------------
Core WPAN changes:
* Support for active scans
* Support for answering BEACON_REQ
* Specific MLME handling for limited devices
WPAN driver changes:
* ca8210:
- Flag the devices as limited
- Remove stray gpiod_unexport() call
----------------------------------------------------------------
Andy Shevchenko (1):
ieee802154: ca8210: Remove stray gpiod_unexport() call
Miquel Raynal (7):
ieee802154: Add support for user active scan requests
mac802154: Handle active scanning
ieee802154: Add support for allowing to answer BEACON_REQ
mac802154: Handle received BEACON_REQ
net: ieee802154: Handle limited devices with only datagram support
ieee802154: ca8210: Flag the driver as being limited
Merge tag 'v6.4-rc4' into wpan-next/staging
drivers/net/ieee802154/ca8210.c | 4 ++--
include/net/cfg802154.h | 3 +++
include/net/ieee802154_netdev.h | 20 +++++++++++++++++++-
net/ieee802154/header_ops.c | 36 ++++++++++++++++++++++++++++++++++++
net/ieee802154/nl802154.c | 13 ++++++++++++-
net/mac802154/ieee802154_i.h | 21 +++++++++++++++++++++
net/mac802154/main.c | 2 ++
net/mac802154/rx.c | 70 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-
net/mac802154/scan.c | 68 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++------
9 files changed, 226 insertions(+), 11 deletions(-)
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: pull-request: ieee802154 for net-next 2023-06-23
2023-06-23 17:55 pull-request: ieee802154 for net-next 2023-06-23 Miquel Raynal
@ 2023-06-24 22:59 ` Jakub Kicinski
2023-06-26 10:39 ` Miquel Raynal
0 siblings, 1 reply; 3+ messages in thread
From: Jakub Kicinski @ 2023-06-24 22:59 UTC (permalink / raw)
To: Miquel Raynal; +Cc: davem, pabeni, alex.aring, stefan, netdev, linux-wpan
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).
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: pull-request: ieee802154 for net-next 2023-06-23
2023-06-24 22:59 ` Jakub Kicinski
@ 2023-06-26 10:39 ` Miquel Raynal
0 siblings, 0 replies; 3+ messages in thread
From: Miquel Raynal @ 2023-06-26 10:39 UTC (permalink / raw)
To: Jakub Kicinski; +Cc: davem, pabeni, alex.aring, stefan, netdev, linux-wpan
Hi Jakub,
kuba@kernel.org wrote on Sat, 24 Jun 2023 15:59:47 -0700:
> 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).
I agree merging upstream tags darkens the history. So IIUC, it's fine
to have an -rc tag higher than -rc1 as base, but you prefer to receive
one merge request per "base tag". Duly noted.
Thanks!
Miquèl
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-06-26 10:40 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-06-23 17:55 pull-request: ieee802154 for net-next 2023-06-23 Miquel Raynal
2023-06-24 22:59 ` Jakub Kicinski
2023-06-26 10:39 ` Miquel Raynal
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.