From: "Danilo Krummrich" <dakr@kernel.org>
To: "Mark Brown" <broonie@kernel.org>
Cc: "Greg KH" <greg@kroah.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-next@vger.kernel.org>
Subject: Re: Missing signoff in the driver-core tree
Date: Mon, 03 Aug 2026 20:59:38 +0200 [thread overview]
Message-ID: <DKFJG2CUQNTO.1920BDJLFN0UY@kernel.org> (raw)
In-Reply-To: <36b6f2b8-f5dd-4629-b3d8-17f1b884594c@sirena.org.uk>
On Mon Aug 3, 2026 at 7:25 PM CEST, Mark Brown wrote:
> This issue is still present today.
Thanks for reporting; as mentioned this is from dropping an unrelated broken
preceeding commit from driver-core-testing.
So, technically those commits got rebased before things were propagated to
driver-core-next. However, we are usually not rewriting the history of
driver-core-next.
Again, sorry about that.
prev parent reply other threads:[~2026-08-03 18:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-26 17:34 Missing signoff in the driver-core tree Mark Brown
2026-07-26 18:30 ` Danilo Krummrich
2026-08-03 17:25 ` Mark Brown
2026-08-03 18:59 ` Danilo Krummrich [this message]
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=DKFJG2CUQNTO.1920BDJLFN0UY@kernel.org \
--to=dakr@kernel.org \
--cc=broonie@kernel.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rafael@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