From: Mark Brown <broonie@kernel.org>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
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 13:08:44 +0100 [thread overview]
Message-ID: <atdZzEMsMWhzO2gO@sirena.co.uk> (raw)
In-Reply-To: <e1119f07-83cc-8178-3c6a-e87778d3cb16@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 753 bytes --]
On Tue, Oct 20, 2026 at 02:07:02PM +0300, Ilpo Järvinen wrote:
> 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
> 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
That's what I fetched yesterday, I don't know if there was some infra
issue which caused the fetch to fail. What I'm seeing for today is
commit 893018d51f27ec0449155b0afe371aaf65380630, hopefully that's what
you expected.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-10-20 12:08 UTC|newest]
Thread overview: 12+ 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
2026-10-13 11:33 ` Mark Brown
2026-10-19 19:08 ` Mark Brown
2026-10-20 11:07 ` Ilpo Järvinen
2026-10-20 12:08 ` Mark Brown [this message]
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=atdZzEMsMWhzO2gO@sirena.co.uk \
--to=broonie@kernel.org \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--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