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, 20 Oct 2026 14:07:02 +0300 (EEST) [thread overview]
Message-ID: <e1119f07-83cc-8178-3c6a-e87778d3cb16@linux.intel.com> (raw)
In-Reply-To: <atZqoXnT_27rGAn9@sirena.co.uk>
On Mon, 19 Oct 2026, Mark Brown wrote:
> On Mon, Oct 12, 2026 at 08:03:17PM +0100, 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?
>
> And today.
Hi Mark,
Something odd is likely going on here. Neither of those commits above are
in my tree anymore.
Your latest merge:
commit 233956951080612ff68d0c54f620606c53a1c91c
Merge: 67f116b3a9f8 98f039265e58
Author: Mark Brown <broonie@kernel.org>
AuthorDate: Mon Oct 19 17:58:11 2026 +0100
Commit: Mark Brown <broonie@kernel.org>
CommitDate: Mon Oct 19 17:58:11 2026 +0100
Merge branch 'for-next' of https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git
I don't know how you got that 98f039265e58 but that hasn't been in pdx86
tree for multiple days by now:
https://git.kernel.org/pub/scm/infra/transparency-logs/gitolite/git/1.git/commit/?id=1bd7f5b78426fd94a4a3f75c79835a4416809e87
$ git log ea40f1e9f07aab937b9a217633be7a1f66260394 | grep -e 4dabecbb202e8 -e 9af7fddef448d
--
i.
next prev parent reply other threads:[~2026-10-20 11:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 10:53 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
2026-10-13 11:33 ` Mark Brown
2026-10-19 19:08 ` Mark Brown
2026-10-20 11:07 ` Ilpo Järvinen [this message]
2026-10-20 12:08 ` Mark Brown
2026-10-20 12:59 ` Ilpo Järvinen
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=e1119f07-83cc-8178-3c6a-e87778d3cb16@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
all inboxes | Powered by JetHome®