From: "Michał Górny" <mgorny@gentoo.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH linux-5.10.y 1/5] ASoC: Intel: bxt_da7219_max98357a: shrink platform_id below 20 characters
Date: Mon, 01 Sep 2025 15:55:29 +0200 [thread overview]
Message-ID: <6369adc8dee031617e5561e56b6e48c5edbe1f03.camel@gentoo.org> (raw)
In-Reply-To: <2025090101-exert-deceased-3071@gregkh>
[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]
On Mon, 2025-09-01 at 15:25 +0200, Greg KH wrote:
> On Mon, Sep 01, 2025 at 11:54:36AM +0200, Michał Górny wrote:
> > From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
> >
> > commit 24e46fb811e991f56d5694b10ae7ceb8d2b8c846 upstream.
> >
> > The excessive platform id lengths are causing out-of-buffer reads
> > in depmod, e.g.:
> >
> > depmod: FATAL: Module index: bad character '�'=0x80 - only 7-bit ASCII is supported:
> > platform:jsl_rt5682_max98360ax�
> >
> > Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
> > Link: https://lore.kernel.org/r/20210511213707.32958-5-pierre-louis.bossart@linux.intel.com
> > Signed-off-by: Mark Brown <broonie@kernel.org>
> > Signed-off-by: Michał Górny <mgorny@gentoo.org>
>
> This commit text does not match the upstream commit text at all :(
>
> Same for others in this series, please fix.
I'm sorry, I've misread the instructions as telling me to describe why I
believe this deserves to be backported. It would be really helpful if
they linked to some good examples. Should I also keep the original
Reviewed-by lines?
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 512 bytes --]
next prev parent reply other threads:[~2025-09-01 13:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 6:03 5.10 backport request: ASoC: Intel: sof_rt5682: shrink platform_id names below 20 characters Michał Górny
2025-08-29 7:09 ` Michał Górny
2025-08-29 13:55 ` Greg KH
2025-08-31 18:25 ` Michał Górny
2025-09-01 5:34 ` Greg KH
2025-09-01 9:54 ` [PATCH linux-5.10.y 1/5] ASoC: Intel: bxt_da7219_max98357a: shrink platform_id " Michał Górny
2025-09-01 9:54 ` [PATCH linux-5.10.y 2/5] ASoC: Intel: sof_rt5682: shrink platform_id names " Michał Górny
2025-09-01 9:54 ` [PATCH linux-5.10.y 3/5] ASoC: Intel: glk_rt5682_max98357a: shrink platform_id " Michał Górny
2025-09-01 9:54 ` [PATCH linux-5.10.y 4/5] ASoC: Intel: sof_da7219_max98373: " Michał Górny
2025-09-01 9:54 ` [PATCH linux-5.10.y 5/5] ASoC: Intel: sof_da7219_mx98360a: fail to initialize soundcard Michał Górny
2025-09-01 13:25 ` [PATCH linux-5.10.y 1/5] ASoC: Intel: bxt_da7219_max98357a: shrink platform_id below 20 characters Greg KH
2025-09-01 13:55 ` Michał Górny [this message]
2025-09-01 13:59 ` Greg KH
2025-09-01 14:10 ` [PATCH v2 " Michał Górny
2025-09-01 14:10 ` [PATCH v2 linux-5.10.y 2/5] ASoC: Intel: sof_rt5682: shrink platform_id names " Michał Górny
2025-09-01 14:10 ` [PATCH v2 linux-5.10.y 3/5] ASoC: Intel: glk_rt5682_max98357a: shrink platform_id " Michał Górny
2025-09-01 14:10 ` [PATCH v2 linux-5.10.y 4/5] ASoC: Intel: sof_da7219_max98373: " Michał Górny
2025-09-01 14:10 ` [PATCH v2 linux-5.10.y 5/5] ASoC: Intel: sof_da7219_mx98360a: fail to initialize soundcard Michał Górny
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=6369adc8dee031617e5561e56b6e48c5edbe1f03.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gregkh@linuxfoundation.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 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).