All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Mark Brown <broonie@debian.org>,
	Thierry Reding <thierry.reding@kernel.org>
Cc: Breno Leitao <leitao@debian.org>,
	ksummit@lists.linux.dev, linux-next@vger.kernel.org
Subject: Re: [MAINTAINERS SUMMIT] Any feedback for -next?
Date: Thu, 13 Aug 2026 13:57:06 +0200	[thread overview]
Message-ID: <5f2a67a2-a8ca-41c5-a4e2-2cac34c1f8d3@kernel.org> (raw)
In-Reply-To: <88c68516-9402-462f-9b5a-df7123f220e9@sirena.org.uk>

On 13/08/2026 13:25, Mark Brown wrote:
> On Thu, Aug 13, 2026 at 11:59:19AM +0200, Thierry Reding wrote:
>> On Wed, Aug 12, 2026 at 04:42:21AM -0700, Breno Leitao wrote:
> 
>>> Would getting rid of these ephemeral commits make linux-next easier
>>> to work with?
> 
>> I think this is a problem that we can easily address using tools. next
>> already has scripts to detect these issues and I think perhaps we can
>> provide a variant of those in a way that would allow people to set them
>> up in their tree as maybe git hooks so they automatically get run on
>> pre-push or something.
> 
> Krzysztof Kozlowski did a bunch of scripts/hooks that the soc tree
> people use, that's probably an easy thing for people to integrate,
> though since I don't have the URL to hand I guess it needs more
> publicity.

Here's the most recent variant of the toolset I collected from Greg and
Steven + a few new (like to avoid back-merging b4 branches which did
happen in the past... remember the day b4 was non-working for every
contributor using mainline kernel?):
https://web.git.kernel.org//pub/scm/linux/kernel/git/soc/soc-tools.git


The hooks are trivial to setup, I even added install.sh, so honestly
having incorrect "Fixes" tags or missing SoB by the maintainer cannot be
excused really.

I was describing them in my speech about maintainer's toolbox 3 years ago:
https://lpc.events/event/17/contributions/1498/


Best regards,
Krzysztof

      reply	other threads:[~2026-08-13 11:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-11 16:54 [MAINTAINERS SUMMIT] Any feedback for -next? Mark Brown
2026-08-11 19:31 ` Geert Uytterhoeven
2026-08-12 11:19 ` Uwe Kleine-König
2026-08-12 16:37   ` Mark Brown
2026-08-12 16:45     ` Sasha Levin
2026-08-12 17:02       ` Mark Brown
2026-08-13  7:31     ` Geert Uytterhoeven
2026-08-13  9:19       ` Uwe Kleine-König
2026-08-13 12:36       ` Mark Brown
2026-08-12 11:42 ` Breno Leitao
2026-08-12 15:27   ` Steven Rostedt
2026-08-12 15:59     ` Lee Jones
2026-08-12 17:10       ` Guenter Roeck
2026-08-12 17:14         ` Arnaldo Carvalho de Melo
2026-08-12 17:37           ` Guenter Roeck
2026-08-12 19:40             ` Arnaldo Carvalho de Melo
2026-08-13  9:59   ` Thierry Reding
2026-08-13 11:25     ` Mark Brown
2026-08-13 11:57       ` Krzysztof Kozlowski [this message]

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=5f2a67a2-a8ca-41c5-a4e2-2cac34c1f8d3@kernel.org \
    --to=krzk@kernel.org \
    --cc=broonie@debian.org \
    --cc=ksummit@lists.linux.dev \
    --cc=leitao@debian.org \
    --cc=linux-next@vger.kernel.org \
    --cc=thierry.reding@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.