Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: alsa-devel@alsa-project.org, kernel-janitors@vger.kernel.org,
	Takashi Iwai <tiwai@suse.com>,
	Allison Randal <allison@lohutok.net>
Subject: Re: [PATCH] ALSA: usb-audio: Fix a limit check in proc_dump_substream_formats()
Date: Wed, 22 Apr 2020 11:29:42 +0200	[thread overview]
Message-ID: <s5h8sin27i1.wl-tiwai@suse.de> (raw)
In-Reply-To: <20200422092255.GB195357@mwanda>

On Wed, 22 Apr 2020 11:22:55 +0200,
Dan Carpenter wrote:
> 
> This should be ARRAY_SIZE() instead of sizeof().  The sizeof() limit is
> too high so it doesn't work.
> 
> Fixes: 093b8494f299 ("ALSA: usb-audio: Print more information in stream proc files")
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>

Thanks, applied.


Takashi

      reply	other threads:[~2020-04-22  9:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-22  9:22 [PATCH] ALSA: usb-audio: Fix a limit check in proc_dump_substream_formats() Dan Carpenter
2020-04-22  9:29 ` Takashi Iwai [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=s5h8sin27i1.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=allison@lohutok.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=dan.carpenter@oracle.com \
    --cc=kernel-janitors@vger.kernel.org \
    --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