From: Greg KH <gregkh@linuxfoundation.org>
To: Akshay Gujar <Akshay.Gujar@harman.com>
Cc: linux-usb@vger.kernel.org, stern@rowland.harvard.edu,
oneukum@suse.com, linux-kernel@vger.kernel.org,
naveen.v@harman.com, sankarkumar.krishnasamy@harman.com
Subject: Re: [PATCH v2 2/3] Documentation: ABI: document DEVICE_ENUMERATION_FAILURE uevent
Date: Wed, 7 Jan 2026 16:02:29 +0100 [thread overview]
Message-ID: <2026010748-shrivel-curliness-755d@gregkh> (raw)
In-Reply-To: <20251224115808.415753-3-Akshay.Gujar@harman.com>
On Wed, Dec 24, 2025 at 11:58:07AM +0000, Akshay Gujar wrote:
> Document the DEVICE_ENUMERATION_FAILURE uevent emitted when device
> enumeration fails, including a minimal example captured on USB.
>
> Signed-off-by: Akshay Gujar <Akshay.Gujar@harman.com>
> ---
> Documentation/ABI/testing/sysfs-uevent | 22 ++++++++++++++++++++++
> 1 file changed, 22 insertions(+)
>
> diff --git a/Documentation/ABI/testing/sysfs-uevent b/Documentation/ABI/testing/sysfs-uevent
> index 0b6227706b35..1f1573c8be96 100644
> --- a/Documentation/ABI/testing/sysfs-uevent
> +++ b/Documentation/ABI/testing/sysfs-uevent
> @@ -49,3 +49,25 @@ Description:
>
> Users:
> udev, userspace tools generating synthetic uevents
> +
> +What: DEVICE_ENUMERATION_FAILURE
> +Date: Dec 2025
It's not December anymore :)
> +KernelVersion: 6.x
Are you sure this will happen? And the major number means nothing,
let's pick the real release number please.
thanks,
greg k-h
next prev parent reply other threads:[~2026-01-07 15:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250221102949.1135849-1-Akshay.Gujar@harman.com>
2025-02-21 10:53 ` [PATCH] usb: core: notify unrecognized usb device Greg KH
[not found] ` <20250826165244.22283-1-Akshay.Gujar@harman.com>
2025-09-06 12:28 ` Greg KH
2025-09-08 8:58 ` Oliver Neukum
2025-09-08 9:04 ` Greg KH
[not found] ` <20250918172355.5118-1-Akshay.Gujar@harman.com>
2025-10-08 11:08 ` Greg KH
[not found] ` <20251224115808.415753-1-Akshay.Gujar@harman.com>
[not found] ` <20251224115808.415753-2-Akshay.Gujar@harman.com>
2026-01-07 15:01 ` [PATCH v2 1/3] driver core: add device_enumeration_failure_notify() helper Greg KH
2026-01-07 15:01 ` [PATCH v2 0/3] Generic device enumeration failure notification Greg KH
[not found] ` <20251224115808.415753-3-Akshay.Gujar@harman.com>
2026-01-07 15:02 ` Greg KH [this message]
[not found] ` <20251224115808.415753-4-Akshay.Gujar@harman.com>
2026-01-07 15:03 ` [PATCH v2 3/3] usb: hub: send enumeration failure uevent Greg KH
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=2026010748-shrivel-curliness-755d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Akshay.Gujar@harman.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=naveen.v@harman.com \
--cc=oneukum@suse.com \
--cc=sankarkumar.krishnasamy@harman.com \
--cc=stern@rowland.harvard.edu \
/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