Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Richard Fitzgerald <rf@opensource.cirrus.com>
Cc: Thorsten Blum <thorsten.blum@linux.dev>,
	Mark Brown <broonie@kernel.org>,
	David Rhodes <david.rhodes@cirrus.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	Kees Cook <kees@kernel.org>,
	"Gustavo A. R. Silva" <gustavoars@kernel.org>,
	linux-sound@vger.kernel.org, patches@opensource.cirrus.com,
	linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH] ASoC: cs-amp-lib: Annotate struct cirrus_amp_efi_data with __counted_by()
Date: Tue, 15 Apr 2025 14:07:15 +0200	[thread overview]
Message-ID: <87ecxtzkzw.wl-tiwai@suse.de> (raw)
In-Reply-To: <c344e6bd-1a95-4982-927d-f679410c444b@opensource.cirrus.com>

On Tue, 15 Apr 2025 14:03:18 +0200,
Richard Fitzgerald wrote:
> 
> On 15/04/2025 12:51 pm, Thorsten Blum wrote:
> > On 15. Apr 2025, at 12:56, Mark Brown wrote:
> >> On Tue, Apr 15, 2025 at 11:03:55AM +0200, Thorsten Blum wrote:
> >>> Add the __counted_by() compiler attribute to the flexible array member
> >>> 'data' to improve access bounds-checking via CONFIG_UBSAN_BOUNDS and
> >>> CONFIG_FORTIFY_SOURCE.
> >> 
> >> As documented in submitting-patches.rst please send patches to the
> >> maintainers for the code you would like to change.  The normal kernel
> >> workflow is that people apply patches from their inboxes, if they aren't
> >> copied they are likely to not see the patch at all and it is much more
> >> difficult to apply patches.
> > 
> > I just use whatever scripts/get_maintainer.pl outputs. Maybe the
> > MAINTAINERS file should be updated?
> > 
> > Best,
> > Thorsten
> > 
> 
> MAINTAINERS only lists Takashi and Jaroslav as maintainers of
> include/sound/*.
> 
> A separate section lists Mark as maintainer of a specific set of files
> within include/sound/
> 
> I guess any files we put in include/sound that are for an ASoC driver
> have to also be added to Mark's ASoC section of MAINTAINERS?

Yes, it makes sense.


Takashi

  reply	other threads:[~2025-04-15 12:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-15  9:03 [PATCH] ASoC: cs-amp-lib: Annotate struct cirrus_amp_efi_data with __counted_by() Thorsten Blum
2025-04-15  9:24 ` Richard Fitzgerald
2025-04-15 10:56 ` Mark Brown
2025-04-15 11:51   ` Thorsten Blum
2025-04-15 12:03     ` Richard Fitzgerald
2025-04-15 12:07       ` Takashi Iwai [this message]
2025-04-15 14:36 ` Mark Brown

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=87ecxtzkzw.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=broonie@kernel.org \
    --cc=david.rhodes@cirrus.com \
    --cc=gustavoars@kernel.org \
    --cc=kees@kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=perex@perex.cz \
    --cc=rf@opensource.cirrus.com \
    --cc=thorsten.blum@linux.dev \
    --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