From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, sumanth.gavini@yahoo.com
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1] HID: mcp2221: Set driver data before I2C adapter add
Date: Tue, 29 Jul 2025 22:42:54 -0400 [thread overview]
Message-ID: <20250716200658-fbf1063f2e8bf820@stable.kernel.org> (raw)
In-Reply-To: <20250716195316.176786-1-sumanth.gavini@yahoo.com>
[ Sasha's backport helper bot ]
Hi,
Summary of potential issues:
⚠️ Found matching upstream commit but patch is missing proper reference to it
Found matching upstream commit: f2d4a5834638bbc967371b9168c0b481519f7c5e
WARNING: Author mismatch between patch and found commit:
Backport author: Sumanth Gavini<sumanth.gavini@yahoo.com>
Commit author: Hamish Martin<hamish.martin@alliedtelesis.co.nz>
Status in newer kernel trees:
6.15.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (different SHA1: 2afe67cfe8f1)
Note: The patch differs from the upstream commit:
---
1: f2d4a5834638b < -: ------------- HID: mcp2221: Set driver data before I2C adapter add
-: ------------- > 1: f2198ea7eb3e7 Linux 6.1.145
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.1.y | Success | Success |
prev parent reply other threads:[~2025-07-30 2:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250716195316.176786-1-sumanth.gavini.ref@yahoo.com>
2025-07-16 19:53 ` [PATCH 6.1] HID: mcp2221: Set driver data before I2C adapter add Sumanth Gavini
2025-07-16 20:34 ` kernel test robot
2025-07-17 0:01 ` [PATCH V2 " Sumanth Gavini
2025-07-18 1:34 ` Sasha Levin
2025-07-18 2:36 ` [PATCH v3 " Sumanth Gavini
2025-07-30 2:42 ` Sasha Levin [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=20250716200658-fbf1063f2e8bf820@stable.kernel.org \
--to=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=sumanth.gavini@yahoo.com \
/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;
as well as URLs for NNTP newsgroup(s).