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: Sun, 26 Jul 2026 20:30:57 +0200 [thread overview]
Message-ID: <DK8PTQY0VC38.26J99W74ACFTQ@kernel.org> (raw)
In-Reply-To: <amZFO8eUhS9xhfCs@sirena.org.uk>
On Sun Jul 26, 2026 at 7:34 PM CEST, Mark Brown wrote:
> Commits
>
> 4e63c0582e2ae ("base: Remove unused DMA_FENCE_TRACE Kconfig symbol")
> 45dfa004893df ("driver core: soc: Unregister bus on early device registration failure")
> ba3dedcf3bd47 ("software node: Fix software_node_get_reference_args() with index -1")
> c3a280ff728a9 ("debugfs: warn if file creation failed due to uninitialized debugfs")
> 06553566a841c ("kernfs: Replace strcpy(s, "../") with memcpy(s, "../", 4)")
> d996995a0ffb8 ("kernfs: simplify kernfs_name_hash()")
> 32e21e9509915 ("docs: ABI: sysfs-uevent: add missing bracket")
> 38f5745f49e44 ("arch_numa: remove redundant nodemask clears in numa_init()")
> 8cfe7ad274bb4 ("driver core: attribute_container: Unwind device_add() on attr failure")
> 6e328b4a208f7 ("drivers: base: Remove statistics group if encryption group not created")
> c37ab60d55e34 ("device property: Refactor to use RAII approach")
> 1900692555826 ("device property: fix infinite loop in fwnode_for_each_child_node()")
> 10864921212fc ("driver core: avoid repeatedly printing the same 'Fixed dependency' log")
>
> are missing a Signed-off-by from their committers
Ah, that's because an unrelated preceding patch that was reported to break the
build by 0-day was dropped from driver-core-testing, so those commits
technically got rebased before they hit driver-core-next. Sorry about that.
prev parent reply other threads:[~2026-07-26 18:31 UTC|newest]
Thread overview: 2+ 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 [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=DK8PTQY0VC38.26J99W74ACFTQ@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.