Linux-Next discussions
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Hans de Goede <hansg@kernel.org>
Cc: Mark Brown <broonie@kernel.org>,
	Mark Gross <markgross@kernel.org>,
	 LKML <linux-kernel@vger.kernel.org>,
	linux-next@vger.kernel.org
Subject: Re: Missing signoff in the drivers-x86 tree
Date: Tue, 13 Oct 2026 14:05:41 +0300 (EEST)	[thread overview]
Message-ID: <d1fa9d26-ba44-5cd5-76cc-1fc91ba9a6d8@linux.intel.com> (raw)
In-Reply-To: <44fe29ee-9692-49f4-aaa7-7201c9cdcaba@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 1510 bytes --]

On Tue, 13 Oct 2026, Hans de Goede wrote:
> On 13-Oct-26 10:34, Ilpo Järvinen wrote:
> > On Mon, 12 Oct 2026, Mark Brown wrote:
> > 
> >> On Mon, Oct 05, 2026 at 02:52:50PM +0200, Mark Brown wrote:
> >>> On Mon, Sep 28, 2026 at 03:37:30PM +0100, Mark Brown wrote:
> >>>> On Thu, Sep 24, 2026 at 11:53:54AM +0100, Mark Brown wrote:
> >>>>> Commits
> >>>>>
> >>>>>   4dabecbb202e8 ("platform/x86: hp-wmi: add Omen Transcend 14 8C58 support")
> >>>>>   9af7fddef448d ("platform/x86: asus-wmi: suppress -ENODEV warning in fan_curve_get_factory_default()")
> >>>>>
> >>>>> are missing a Signed-off-by from their authors
> >>>>
> >>>> This issue is still present today.
> >>>
> >>> And today.
> >>
> >> And today - should Ilpo be added to the list of contacts for this tree?
> > 
> > Yeah, I'm in practice the person who is handling pdx86 patches these days 
> > so it would be good.
> > 
> > ...Goes to do some massive history rewriting...
> 
> My bad, I missed you (Ilpo) were not getting these emails, sorry.

I finally went and improved my patch getting script to block any 
submissions for which git interpret-trailers shows no Sign-off-by lines.
That'll make it in practice impossible for me to apply such submissions 
anymore.

It's not entirely foolproof though as the Signed-off-by could still be 
invalid one e.g. by being different from From and I don't know easy way to 
extract From from a patch file (consider encodings and multiple From 
lines properly).

-- 
 i.

  reply	other threads:[~2026-10-13 11:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-24 10:53 Missing signoff in the drivers-x86 tree Mark Brown
2026-09-28 14:37 ` Mark Brown
2026-10-05 12:52   ` Mark Brown
2026-10-12 19:03     ` Mark Brown
2026-10-13  8:34       ` Ilpo Järvinen
2026-10-13  8:46         ` Hans de Goede
2026-10-13 11:05           ` Ilpo Järvinen [this message]
2026-10-13 11:33             ` Mark Brown

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=d1fa9d26-ba44-5cd5-76cc-1fc91ba9a6d8@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=broonie@kernel.org \
    --cc=hansg@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=markgross@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