From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Hans de Goede <hansg@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 11:34:29 +0300 (EEST) [thread overview]
Message-ID: <8f4e200a-c2fd-29c6-ee4d-a91137b90c12@linux.intel.com> (raw)
In-Reply-To: <1a363159-02b9-4644-9cc8-38e210d97d5d@sirena.org.uk>
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...
--
i.
next prev parent reply other threads:[~2026-10-13 8:34 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 [this message]
2026-10-13 8:46 ` Hans de Goede
2026-10-13 11:05 ` Ilpo Järvinen
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=8f4e200a-c2fd-29c6-ee4d-a91137b90c12@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