From: Philipp Stanner <phasta@mailbox.org>
To: tanze <tanze@kylinos.cn>,
perex@perex.cz, tiwai@suse.com, phasta@kernel.org,
linux-sound@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: maestro3: using vmalloc_array() to handle the code
Date: Wed, 22 Oct 2025 11:56:08 +0200 [thread overview]
Message-ID: <9034243532d090cd51508375510dc03e90e57981.camel@mailbox.org> (raw)
In-Reply-To: <20251022092339.551438-1-tanze@kylinos.cn>
On Wed, 2025-10-22 at 17:23 +0800, tanze wrote:
> Change array_size() to vmalloc_array(), Due to vmalloc_array()
s/Due/due
> is optimized better,uses fewer instructions, and handles
s/is/being
s/,/, /
s/uses/using
s/handles/handling
> overflow more concisely
full stop: '.'
>
> Signed-off-by: tanze <tanze@kylinos.cn>
Is that your full name? Signed-off-by is basically a 'legal' statement
declaring that you as the code's author agree with the license and
stuff and declare that you're allowed (by your employer for example) to
upstream this code.
P.
> ---
> sound/pci/maestro3.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/sound/pci/maestro3.c b/sound/pci/maestro3.c
> index bddf47a1f263..3353980d5cd8 100644
> --- a/sound/pci/maestro3.c
> +++ b/sound/pci/maestro3.c
> @@ -2571,9 +2571,9 @@ snd_m3_create(struct snd_card *card, struct pci_dev *pci,
>
> if (IS_ENABLED(CONFIG_PM_SLEEP)) {
> chip->suspend_mem =
> - vmalloc(array_size(sizeof(u16),
> - REV_B_CODE_MEMORY_LENGTH +
> - REV_B_DATA_MEMORY_LENGTH));
> + vmalloc_array(REV_B_CODE_MEMORY_LENGTH +
> + REV_B_DATA_MEMORY_LENGTH,
> + sizeof(u16));
> if (!chip->suspend_mem)
> dev_warn(card->dev, "can't allocate apm buffer\n");
> }
prev parent reply other threads:[~2025-10-22 9:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 9:23 tanze
2025-10-22 9:56 ` Philipp Stanner [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=9034243532d090cd51508375510dc03e90e57981.camel@mailbox.org \
--to=phasta@mailbox.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=phasta@kernel.org \
--cc=tanze@kylinos.cn \
--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
all inboxes | Powered by JetHome®