Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Geraldo Nascimento <geraldogabriel@gmail.com>
Cc: "Alexander A. Klimov" <grandmaster@al2klimov.de>,
	Nick Li <nick.li@foursemi.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	linux-sound@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] ASoC: codecs: fs210x: fix possible buffer overflow
Date: Wed, 13 May 2026 23:56:51 +0900	[thread overview]
Message-ID: <agSRM7ua38bI4ZPY@sirena.co.uk> (raw)
In-Reply-To: <agPmOSjHXOmpy2FJ@geday>

[-- Attachment #1: Type: text/plain, Size: 409 bytes --]

On Tue, May 12, 2026 at 11:47:21PM -0300, Geraldo Nascimento wrote:
> On Wed, May 13, 2026 at 10:36:32AM +0900, Mark Brown wrote:

> > This doesn't apply against current code, please check and resend.

> Do you mean the codechange must be explicit in the commit message
> instead of a generic pseudocode version?

No.  I mean your patch cannot be applied, I've no idea what it's against
but it's not my tree.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2026-05-13 14:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11 20:35 [PATCH] ASoC: codecs: fs210x: fix possible buffer overflow Alexander A. Klimov
2026-05-12 12:33 ` Mark Brown
2026-05-12 19:07   ` [PATCH v2] " Alexander A. Klimov
2026-05-13  1:36     ` Mark Brown
2026-05-13  2:47       ` Geraldo Nascimento
2026-05-13 14:56         ` Mark Brown [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=agSRM7ua38bI4ZPY@sirena.co.uk \
    --to=broonie@kernel.org \
    --cc=geraldogabriel@gmail.com \
    --cc=grandmaster@al2klimov.de \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=nick.li@foursemi.com \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.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