From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: Mark Brown <broonie@kernel.org>, 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-fixes tree
Date: Tue, 20 Jan 2026 17:34:20 +0200 (EET) [thread overview]
Message-ID: <0d48ec5f-41a2-8482-3612-858fc9581dba@linux.intel.com> (raw)
In-Reply-To: <2a987ffa-e40c-453e-a54a-97a4ce8f8341@amd.com>
[-- Attachment #1: Type: text/plain, Size: 986 bytes --]
On Tue, 20 Jan 2026, Mario Limonciello wrote:
> On 1/20/26 8:37 AM, Ilpo Järvinen wrote:
> > On Tue, 20 Jan 2026, Mark Brown wrote:
> >
> > > Commit
> > >
> > > bb820f17b68f6 ("platform/x86: hp-bioscfg: Fix kernel panic in
> > > GET_INSTANCE_ID macro")
> > >
> > > is missing a Signed-off-by from its author
> >
> > Thanks for the heads up.
> >
> > The patch was submitted with Signed-off-by but git interpret-trailers
> > --in-place
> > seems to mess the tag up for some reason.
> >
>
> I think it's my fault, I wrote the commit message in another text editor when
> I was reformatting the kernel trace back and when I copied and pasted there
> was a spurious " that messed up parsing the S-o-b.
>
> Feel free to strip the spurious " if it helps.
>
> Sorry about that, and thanks for catching it!
I've already fixed it by copying it manually, and noticed at that time the
extra " which explains why the tools did what they did.
--
i.
next prev parent reply other threads:[~2026-01-20 15:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 14:02 Missing signoff in the drivers-x86-fixes tree Mark Brown
2026-01-20 14:37 ` Ilpo Järvinen
2026-01-20 15:30 ` Mario Limonciello
2026-01-20 15:34 ` Ilpo Järvinen [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-27 12:07 Mark Brown
2026-02-27 14:00 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=0d48ec5f-41a2-8482-3612-858fc9581dba@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=mario.limonciello@amd.com \
--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