Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Lachlan Hodges <lachlan.hodges@morsemicro.com>
Cc: linux-wireless@vger.kernel.org, arien.judge@morsemicro.com,
	 dan.callaghan@morsemicro.com
Subject: Re: pull-request: mm81x-next-2026-07-31
Date: Sun, 02 Aug 2026 18:33:05 +0200	[thread overview]
Message-ID: <c0d041baca23377772791242ce0ef241aaba4112.camel@sipsolutions.net> (raw)
In-Reply-To: <3wboegj7eyorursqi7gftc2s3jqtrfi5fv3k57eoqrr5arxmnh@2jextspacknp> (sfid-20260731_084623_069991_CE483BE5)

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

  reply	other threads:[~2026-08-02 16:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-31  6:46 pull-request: mm81x-next-2026-07-31 Lachlan Hodges
2026-08-02 16:33 ` Johannes Berg [this message]
2026-08-03  5:26   ` Lachlan Hodges
2026-08-03 15:27     ` Jeff Johnson

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=c0d041baca23377772791242ce0ef241aaba4112.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=arien.judge@morsemicro.com \
    --cc=dan.callaghan@morsemicro.com \
    --cc=lachlan.hodges@morsemicro.com \
    --cc=linux-wireless@vger.kernel.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