From: Stefan Schmidt <stefan@datenfreihafen.org>
To: Paolo Bonzini <pbonzini@redhat.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
workflows@vger.kernel.org
Cc: Shuah Khan <skhan@linuxfoundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Bjorn Helgaas <helgaas@kernel.org>,
Jiri Kosina <jikos@kernel.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: Kernel development collaboration platform wish list
Date: Tue, 24 Sep 2019 14:20:19 +0200 [thread overview]
Message-ID: <46bd4373-b7e1-6ea6-148c-cc15d881bbfd@datenfreihafen.org> (raw)
In-Reply-To: <8d1c457e-1661-5a5c-69d7-c17d4633b978@redhat.com>
Hello Paolo.
On 24.09.19 11:43, Paolo Bonzini wrote:
> On 17/09/19 20:40, Stefan Schmidt wrote:
>> (c) Git tag sanity checking
>> Some maintainers have scripts for these, but not all. I still see
>> quite some mails about this coming from linux-next checking.
>> 1) ensure SOB by the actual author
>> 2) verify correct SOB/ACK/Reviewed tag usage (funny to see how often
>> things are manually added and gotten slightly wrong)
>> 3) verify Fixes: tag usage (min shasum length, one line without
>> break, etc)
>>
>> There are likely more.
>>
>> Where and how this is to be done I would leave open as this is only
>> requirements collection right now. I just feel that this kind of sanity
>> checking could be easily automated, hopefully without getting into the
>> way of maintainers.
>
> This can be done by a "checkpatch"-like test. If a full-blown
> checkpatch is undesirable (not sure why it would be, though), a special
> mode that only checks headers can be added to the script.
Sure, I do not really mind where this would sit. It is only a tiny piece
and also quite easy to do compared to the more complex building blocks
this will have.
Just brought it up as I have seen it here on there on netdev where a
missing SOB or a wrongly formatted Fixes tag needed some manual labor to
explain it.
regards
Stefan Schmidt
next prev parent reply other threads:[~2019-09-24 12:20 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 8:22 Kernel development collaboration platform wish list Rafael J. Wysocki
2019-09-13 11:13 ` Jani Nikula
2019-09-17 21:58 ` Rafael J. Wysocki
2019-09-18 8:05 ` Jani Nikula
2019-09-18 13:43 ` Steven Rostedt
2019-09-13 11:37 ` Laurent Pinchart
2019-09-13 12:02 ` Geert Uytterhoeven
2019-09-13 12:15 ` Laurent Pinchart
2019-09-13 12:23 ` Geert Uytterhoeven
2019-09-17 22:00 ` Rafael J. Wysocki
2019-10-02 9:30 ` Rafael J. Wysocki
2019-09-17 18:40 ` Stefan Schmidt
2019-09-24 9:43 ` Paolo Bonzini
2019-09-24 12:20 ` Stefan Schmidt [this message]
2019-09-17 22:12 ` Rafael J. Wysocki
2019-10-01 3:52 ` Daniel Axtens
2019-10-01 4:50 ` Andrew Donnellan
2019-10-01 5:04 ` Daniel Axtens
2019-09-23 16:20 ` Theodore Y. Ts'o
2019-09-24 1:39 ` Eric Wong
2019-09-24 5:06 ` Greg Kroah-Hartman
2019-10-01 3:58 ` Daniel Axtens
2019-09-26 10:18 ` Geert Uytterhoeven
2019-09-26 11:40 ` Steven Rostedt
2019-09-26 13:39 ` Geert Uytterhoeven
2019-09-28 22:16 ` Steven Rostedt
2019-09-29 16:03 ` Dmitry Vyukov
2019-09-26 13:10 ` Jani Nikula
2019-09-26 13:41 ` Geert Uytterhoeven
2019-09-26 14:40 ` Jani Nikula
2019-10-02 9:55 ` Rafael J. Wysocki
2019-10-02 14:22 ` Daniel Axtens
2019-10-03 9:23 ` Rafael J. Wysocki
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=46bd4373-b7e1-6ea6-148c-cc15d881bbfd@datenfreihafen.org \
--to=stefan@datenfreihafen.org \
--cc=gregkh@linuxfoundation.org \
--cc=helgaas@kernel.org \
--cc=jikos@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=pbonzini@redhat.com \
--cc=rjw@rjwysocki.net \
--cc=skhan@linuxfoundation.org \
--cc=workflows@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;
as well as URLs for NNTP newsgroup(s).