All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: users@kernel.org, tools@kernel.org
Subject: Re: [b4] initial "b4 dig" to supplant Link: trailers
Date: Sat, 11 Oct 2025 14:39:24 +0200	[thread overview]
Message-ID: <2025101125-supper-fable-e127@gregkh> (raw)
In-Reply-To: <20251010-muscular-camel-of-acumen-00eeaf@lemur>

On Fri, Oct 10, 2025 at 04:47:27PM -0400, Konstantin Ryabitsev wrote:
> Hi, all:
> 
> I just committed the initial implementation of "b4 dig" that will hopefully
> make it easier for maintainers to figure out where a commit came from now that
> we're actively trying to phase out Link: trailers. For now, it only does
> "b4 dig -c [commitish]", e.g. taking some random commits from today:
> 
> Matching the exact patch-id:
> 
> 	$ b4 dig -c ce740955b238761ec1d8cf0590d7e6802d3a813a
> 	Digging into commit ce740955b238761ec1d8cf0590d7e6802d3a813a
> 	Attempting to match by exact patch-id...
> 	Trying to find matching series by patch-id 469ebf2cf560b32106f206e389752deb5f741b6d
> 	Grabbing search results from lore.kernel.org
> 	Found matching series by patch-id
> 	---
> 	This patch is present in the following series:
> 	---
> 	  v3: [PATCH v3] dt-bindings: bus: renesas-bsc: allow additional properties
> 		  https://lore.kernel.org/r/20251009183630.5451-2-wsa+renesas@sang-engineering.com
> 
> No match looking up by exact patch-id (and trying myers, then histogram, then
> patience algorithms with no success):
> 
> 	$ b4 dig -c a29ad21b988652dc60aa99c6d3b1e3d52dc69c30
> 	Digging into commit a29ad21b988652dc60aa99c6d3b1e3d52dc69c30
> 	Attempting to match by exact patch-id...
> 	Trying to find matching series by patch-id abc964d5d53674450f7e553bbe031edc61ac3308
> 	Grabbing search results from lore.kernel.org
> 	Nothing matching that query.
> 	Trying to find matching series by patch-id adf0918395a1a601a8d54d7d26446aadfb6101c2
> 	Grabbing search results from lore.kernel.org
> 	Nothing matching that query.
> 	Attempting to match by author and subject...
> 	Grabbing search results from lore.kernel.org
> 	Found 22 matching messages
> 	---
> 	This patch is present in the following series:
> 	---
> 	  v3: [PATCH v3] tpm: Prevent local DOS via tpm/tpm0/ppi/*operations
> 		  https://lore.kernel.org/r/20250829175152.9704-2-daleksan@redhat.com
> 	  v4: [PATCH v4] tpm: Prevent local DOS via tpm/tpm0/ppi/*operations
> 		  https://lore.kernel.org/r/20250902142429.14041-2-daleksan@redhat.com
> 	  v5: [PATCH v5] tpm: Prevent local DOS via tpm/tpm0/ppi/*operations
> 		  https://lore.kernel.org/r/20250915210829.6661-1-daleksan@redhat.com
> 
> There are known annoyances:
> 
> 1. We don't currently weed out AUTOSEL/stable backports, so older commits may
>    end up in lots of false positives for now. I've not yet figured out how to
>    avoid this without hardcoding it to be kernel-specific.

Because it's not weeding out anything, it seems that any commit that I
pick that is backported just gets confused.

As an example:
	$ b4 dig -c  cfa1a2329a691ffd991fcf7248a57d752e712881 2>&1 | wc -l
	1293

And the end result of that:
	$ b4 dig -c  cfa1a2329a691ffd991fcf7248a57d752e712881 2>&1 | tail -n 5
	---
	This patch is present in the following series:
	---
	  v1: [PATCH 6.1 000/128] 6.1.97-rc1 review
	      https://lore.kernel.org/r/20240702170226.231899085@linuxfoundation.org

Did find the stable review thread, but not all of them?  Is that
intentional?  If you just report all threads it's found in, I'd be happy
as that's what I dig through all the time.

> I'll work on getting that fixed, but for now if you're missing the presence of
> Link: trailers, please test it out.

I'm already missing them :(

And thanks for working on this, if it does end up working well, that's
great.

greg k-h

  reply	other threads:[~2025-10-11 12:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-10 20:47 [b4] initial "b4 dig" to supplant Link: trailers Konstantin Ryabitsev
2025-10-11 12:39 ` Greg KH [this message]
2025-10-13  8:13   ` Peter Zijlstra
2025-10-11 20:08 ` Geert Uytterhoeven
2025-10-11 22:46 ` Linus Torvalds
2025-10-11 23:38   ` Sasha Levin
2025-10-11 23:44     ` Linus Torvalds
2025-10-12  0:39       ` Sasha Levin
2025-10-12 23:17       ` Jason Gunthorpe
2025-10-13 17:12 ` Mark Brown
2025-10-13 17:36   ` Linus Torvalds
2025-10-14 21:17 ` Konstantin Ryabitsev
2025-10-14 21:49   ` Sasha Levin
2025-10-15 13:47     ` Konstantin Ryabitsev
2025-10-14 22:13   ` Mark Brown
2025-10-15 13:44     ` Konstantin Ryabitsev
2025-10-15 13:52       ` Mark Brown
2025-10-15 16:40       ` Rob Herring
2025-10-15  2:52   ` Martin K. Petersen
2025-10-15 13:43     ` Konstantin Ryabitsev
2025-10-15 17:37       ` Martin K. Petersen

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=2025101125-supper-fable-e127@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=tools@kernel.org \
    --cc=users@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 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.