Re: [GIT PULL] wireless-next-2025-09-11

[Jakub Kicinski <kuba@kernel.org>]

On Thu, 11 Sep 2025 19:01:39 +0200 Johannes Berg wrote:
> On Thu, 2025-09-11 at 12:08 +0200, Johannes Berg wrote:
> > Please pull and let us know if there's any problem.  
> 
> Speaking of problems ... we've kept adding Link: tags. If you're going
> to insist we remove them then please just say so explicitly, reject this
> pull request as well if you like, and save everyone the discussion.
> 
> I do truly believe Linus to be wrong on this: assuming a patch has no
> need for any identification/correlation whatsoever before it goes into
> his (or a feeder) tree (and gets a stable sha1) is akin to assuming it
> has no life before it actually ends up there, which I think is
> completely out of touch with reality. But he does ultimately get to
> reject pull requests, so...

Let's see, IMHO links to patch.msgid.link are unambiguously purely to
the posting, not any discussion. I'm planning to try to hack something
up in our patchwork scripts to try to skip applying them when thread is
completely bare, but my next two weekends are quite busy. I'd say
steady as she goes for now..

> Maybe I should make the links go to patchwork, because there you have
> the CI results ... maybe that could be construed as useful information
> in the "Linus sense" (phrased that way because to me the mailing list
> posting is already useful information)?

Maybe. I find ML more useful, but do very occasionally want to look 
at pw. As long as one has the message-id it's not hard to find the pw
entry. I'd recommend against changing the linking to pw. My guess is
that would only lead to increases hostility :)

My personal opinion is that pw-bot already knows the message-id to
commit hash mapping. I was asking K to expose this as some REST
endpoint so that we can trivially script the conversions. But he
suggested (not without sense) that patchwork should serve as our DB,
not 100 random disparate services. One day the netdev foundation will
clear all the organizational hurdles and the PW work will happen :D


unrelated - the wireless PR was already pulled, pw-bot did not respond
🤷️