From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, kees@kernel.org
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH] mod_devicetable: Enlarge the maximum platform_device_id name length
Date: Sat, 5 Jul 2025 17:40:25 -0400 [thread overview]
Message-ID: <20250705153719-a8f20b3a61d3dd27@stable.kernel.org> (raw)
In-Reply-To: <20250415231420.work.066-kees@kernel.org>
[ 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: 655862865c97ff55e4f3f2aaa7708f42f0ea3bd8
Note: The patch differs from the upstream commit:
---
1: 655862865c97f ! 1: b545ae48a3db0 mod_devicetable: Enlarge the maximum platform_device_id name length
@@ Commit message
/* last cacheline: 32 bytes */
};
- Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
- Link: https://lore.kernel.org/r/20250415231420.work.066-kees@kernel.org
Signed-off-by: Kees Cook <kees@kernel.org>
## include/linux/mod_devicetable.h ##
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.15.y | Success | Success |
| stable/linux-6.12.y | Success | Success |
| stable/linux-6.6.y | Success | Success |
| stable/linux-6.1.y | Success | Success |
| stable/linux-5.15.y | Success | Success |
| stable/linux-5.10.y | Success | Success |
| stable/linux-5.4.y | Success | Success |
prev parent reply other threads:[~2025-07-05 21:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 23:14 [PATCH] mod_devicetable: Enlarge the maximum platform_device_id name length Kees Cook
2025-04-16 6:45 ` Andy Shevchenko
2025-07-04 23:49 ` Vitaly Chikunov
2025-04-21 21:30 ` Kees Cook
2025-07-05 21:40 ` 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=20250705153719-a8f20b3a61d3dd27@stable.kernel.org \
--to=sashal@kernel.org \
--cc=kees@kernel.org \
--cc=stable@vger.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.