pull-request: mm81x-next-2026-07-31

pull-request: mm81x-next-2026-07-31

[Lachlan Hodges]

Hi,

This is the first mm81x pull request, so just a single commit for us
to test our workflows using b4/patchwork and all that. Obviously
in the future we'll collect patches overtime like other driver
sub-trees; though I'm sure our pull request cadence will be much lower
at first.

One thing to note is that the tag is not signed, is that something
you need us to do? The docs appear to say that it's really up to the
upstream maintainer.

Let me know if there are any issues etc. Thanks.

lachlan

The following changes since commit 4a0bd262df757b25fc4e2a53c947317c119ced4e:

  wifi: mac80211: fix per-STA profile length in cross-link CSA parsing (2026-07-28 16:04:16 +0200)

are available in the Git repository at:

  https://github.com/MorseMicroLabs/linux-wireless.git tags/mm81x-next-2026-07-31

for you to fetch changes up to 333f7de560e1196034b67db16916b10a0c529e1d:

  wifi: mm81x: prevent timers from outliving teardown (2026-07-31 15:42:49 +1000)

----------------------------------------------------------------

wifi: mm81x: updates - 2026-07-31

- Just a single fix for synchronously shutting down timers to prevent
a UaF.

----------------------------------------------------------------
Linmao Li (1):
      wifi: mm81x: prevent timers from outliving teardown

 drivers/net/wireless/morsemicro/mm81x/mac.c  | 2 +-
 drivers/net/wireless/morsemicro/mm81x/rc.c   | 2 +-
 drivers/net/wireless/morsemicro/mm81x/yaps.c | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

Re: pull-request: mm81x-next-2026-07-31

[Johannes Berg]

On Fri, 2026-07-31 at 16:46 +1000, Lachlan Hodges wrote:
> 
> This is the first mm81x pull request, so just a single commit for us
> to test our workflows using b4/patchwork and all that. Obviously
> in the future we'll collect patches overtime like other driver
> sub-trees; though I'm sure our pull request cadence will be much lower
> at first.

:)

> One thing to note is that the tag is not signed, is that something
> you need us to do? The docs appear to say that it's really up to the
> upstream maintainer.

I guess signed would be nice, if you can arrange it, then I probably
will check less ;-)

It would definitely be good though if you actually created a tag object
with a message, the message you had:

> ----------------------------------------------------------------
> 
> wifi: mm81x: updates - 2026-07-31
> 
> - Just a single fix for synchronously shutting down timers to prevent
> a UaF.
> 
> ----------------------------------------------------------------

wasn't actually in the tag, or you pushed a different one, or something
weird happened? 'git show' on your tag after fetching just shows the
commit it points to.

Anyway I've pulled it and copied that into the merge, but a real tag
message would automatically show up.

Thanks!

johannes

Re: pull-request: mm81x-next-2026-07-31

[Lachlan Hodges]

> I guess signed would be nice, if you can arrange it, then I probably
> will check less ;-)

No problem, I will sort that out.

> It would definitely be good though if you actually created a tag object
> with a message, the message you had:
> 
> > ----------------------------------------------------------------
> > 
> > wifi: mm81x: updates - 2026-07-31
> > 
> > - Just a single fix for synchronously shutting down timers to prevent
> > a UaF.
> > 
> > ----------------------------------------------------------------
> 
> wasn't actually in the tag, or you pushed a different one, or something
> weird happened? 'git show' on your tag after fetching just shows the
> commit it points to.

Oops sorry, yea I created a lightweight tag. Will be sure to do a real
tag next time.

> Anyway I've pulled it and copied that into the merge, but a real tag
> message would automatically show up.

Thanks. Enjoy your holiday :).

lachlan

Re: pull-request: mm81x-next-2026-07-31

[Jeff Johnson]

On 8/2/2026 10:26 PM, Lachlan Hodges wrote:
>> I guess signed would be nice, if you can arrange it, then I probably
>> will check less ;-)
> 
> No problem, I will sort that out.

In case you need the pointer...

https://docs.kernel.org/process/maintainer-pgp-guide.html