From: Takashi Iwai <tiwai@suse.de>
To: David Flater <vger@flaterco.com>
Cc: Jaroslav Kysela <perex@perex.cz>,
LKML <linux-kernel@vger.kernel.org>,
Alsa Devel <alsa-devel@alsa-project.org>
Subject: Re: [PATCHv2 2/2] ALSA: log emu8000 DRAM size at level INFO
Date: Sun, 11 Jan 2015 11:53:40 +0100 [thread overview]
Message-ID: <s5h61cd4mh7.wl-tiwai@suse.de> (raw)
In-Reply-To: <54B077A3.7030703@flaterco.com>
At Fri, 09 Jan 2015 19:51:47 -0500,
David Flater wrote:
>
> Applicable after PATCHv2 1/2:
>
> Detected sound font memory goes unreported unless the kernel was built with
> ALSA debugging enabled. Elevate that to a printk at level INFO.
Nowadays we'd like to avoid use of snd_print*(). Let's use a standard
macro, either dev_info() or pr_info(), instead.
thanks,
Takashi
>
> Signed-off-by: David Flater <dave@flaterco.com>
> ---
> History:
> 2015-01-09 v2: In response to feedback from Takashi Iwai,
> 1. Optimize for diff size.
> 1a. Use goto to avoid indenting.
> 1b. Jettison new debugging printouts.
> 2. Split printk into second patch.
> Retested on CT4390 (4 MiB) and CT4380 (512 KiB).
> 2015-01-08 v1 patch sent to LKML, Alsa Devel and maintainers. Tested on
> unexpanded CT4390 (4 MiB), CT4520 (512 KiB), and CT4380 (512
> KiB).
>
> sound/isa/sb/emu8000.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/sound/isa/sb/emu8000.c b/sound/isa/sb/emu8000.c
> index 3dcf80e..7429a51 100644
> --- a/sound/isa/sb/emu8000.c
> +++ b/sound/isa/sb/emu8000.c
> @@ -451,7 +451,7 @@ size_dram(struct snd_emu8000 *emu)
> snd_emu8000_dma_chan(emu, 0, EMU8000_RAM_CLOSE);
> snd_emu8000_dma_chan(emu, 1, EMU8000_RAM_CLOSE);
>
> - snd_printdd("EMU8000 [0x%lx]: %d Kb on-board memory detected\n",
> + snd_printk(KERN_INFO "EMU8000 [0x%lx]: %d KiB on-board DRAM detected\n",
> emu->port1, size/1024);
>
> emu->mem_size = size;
> --
> 1.8.4
>
prev parent reply other threads:[~2015-01-11 10:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-10 0:51 [PATCHv2 2/2] ALSA: log emu8000 DRAM size at level INFO David Flater
2015-01-11 10:53 ` 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=s5h61cd4mh7.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=vger@flaterco.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