From: Mario Limonciello <superm1@kernel.org>
To: Ai Chao <aichao@kylinos.cn>,
jikos@kernel.org, bentiss@kernel.org, dianders@chromium.org,
treapking@chromium.org, kenkinming2002@gmail.com,
raoxu@uniontech.com
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] HID: i2c-hid: Fixes "(null)" device name error logs in i2c_hid_parse
Date: Thu, 9 Jul 2026 23:19:23 -0500 [thread overview]
Message-ID: <7c76209b-858e-4e20-a867-86bcc8efc198@kernel.org> (raw)
In-Reply-To: <20260710023936.3960010-1-aichao@kylinos.cn>
On 7/9/26 21:39, Ai Chao wrote:
> Hello Doug
>
> "Ai" is my surname, and "Chao" is my given name. My name is Ai Chao, which translates to "Super AI".
>
>>> Before: hid (null): reading report descriptor failed
>>> After: i2c_hid i2c-TPD0001:00: reading report descriptor failed
>>>
>>> Signed-off-by: Ai Chao <aichao@kylinos.cn>
>>> ---
>>> change for v2
>>> - Used Fixes tag.
>
>> Could have fooled me. ;-)
>
> syslog:
> kernel: [ 3.815131][ 1] [ T319] i2c_designware HYGO0010:00: timeout in disabling adapter
> kernel: [ 15.790171][ 1] [ T319] i2c_designware HYGO0010:00: timeout waiting for bus ready
> kernel: [ 15.998769][ 1] [ T319] i2c reading report descriptor failed retry:49
> kernel: [ 16.038176][ 1] [ T319] i2c_designware HYGO0010:00: timeout waiting for bus ready
> kernel: [ 16.246771][ 1] [ T319] i2c reading report descriptor failed retry:50
> kernel: [ 16.246775][ 1] [ T319] hid (null): reading report descriptor failed
> kernel: [ 16.246778][ 1] [ T319] i2c_hid i2c-TPD0001:00: can't add hid device: -5
> kernel: [ 16.246954][ 1] [ T319] i2c_hid: probe of i2c-TPD0001:00 failed with error -5
>
>
> Thanks,
> Ai Chao
>
>
The point was that there is no "Fixes" tag added above your SoB, but you
mentioned that there was one in your changelist. Identify the commit
that you're fixing (use git blame for example) and then add it to the
commit text above your SoB in the correct format.
# git log -1 --format='Fixes: %h ("%s")' $commit
next prev parent reply other threads:[~2026-07-10 4:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 2:39 Re: [PATCH v2] HID: i2c-hid: Fixes "(null)" device name error logs in i2c_hid_parse Ai Chao
2026-07-10 4:19 ` Mario Limonciello [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-07 1:54 Ai Chao
2026-07-07 2:32 ` Doug Anderson
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=7c76209b-858e-4e20-a867-86bcc8efc198@kernel.org \
--to=superm1@kernel.org \
--cc=aichao@kylinos.cn \
--cc=bentiss@kernel.org \
--cc=dianders@chromium.org \
--cc=jikos@kernel.org \
--cc=kenkinming2002@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raoxu@uniontech.com \
--cc=treapking@chromium.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