Re: [MAINTAINERS SUMMIT] Any feedback for -next?
Krzysztof Kozlowski <[email protected]>
| Newsgroups | dev.linux.lists.ksummit,org.kernel.vger.linux-next |
|---|---|
| Message-ID | <[email protected]> |
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