From: Takashi Iwai <tiwai@suse.de>
To: Joonsoo Kim <js1304@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Chris Metcalf <cmetcalf@ezchip.com>,
David Rientjes <rientjes@google.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linux-mm@kvack.org, Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Christoph Lameter <cl@linux.com>,
linux-api@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/5] sound: query dynamic DEBUG_PAGEALLOC setting
Date: Fri, 05 Feb 2016 10:26:59 +0100 [thread overview]
Message-ID: <s5hwpqj1p98.wl-tiwai@suse.de> (raw)
In-Reply-To: <1454565386-10489-4-git-send-email-iamjoonsoo.kim@lge.com>
On Thu, 04 Feb 2016 06:56:24 +0100,
Joonsoo Kim wrote:
>
> We can disable debug_pagealloc processing even if the code is complied
> with CONFIG_DEBUG_PAGEALLOC. This patch changes the code to query
> whether it is enabled or not in runtime.
>
> Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Acked-by: Takashi Iwai <tiwai@suse.de>
Takashi
> ---
> sound/drivers/pcsp/pcsp.c | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/sound/drivers/pcsp/pcsp.c b/sound/drivers/pcsp/pcsp.c
> index 27e25bb..72e2d00 100644
> --- a/sound/drivers/pcsp/pcsp.c
> +++ b/sound/drivers/pcsp/pcsp.c
> @@ -14,6 +14,7 @@
> #include <linux/input.h>
> #include <linux/delay.h>
> #include <linux/bitops.h>
> +#include <linux/mm.h>
> #include "pcsp_input.h"
> #include "pcsp.h"
>
> @@ -148,11 +149,11 @@ static int alsa_card_pcsp_init(struct device *dev)
> return err;
> }
>
> -#ifdef CONFIG_DEBUG_PAGEALLOC
> /* Well, CONFIG_DEBUG_PAGEALLOC makes the sound horrible. Lets alert */
> - printk(KERN_WARNING "PCSP: CONFIG_DEBUG_PAGEALLOC is enabled, "
> - "which may make the sound noisy.\n");
> -#endif
> + if (debug_pagealloc_enabled()) {
> + printk(KERN_WARNING "PCSP: CONFIG_DEBUG_PAGEALLOC is enabled, "
> + "which may make the sound noisy.\n");
> + }
>
> return 0;
> }
> --
> 1.9.1
>
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-02-05 9:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 5:56 [PATCH 0/5] follow-up "Optimize CONFIG_DEBUG_PAGEALLOC" Joonsoo Kim
2016-02-04 5:56 ` [PATCH 1/5] mm/vmalloc: query dynamic DEBUG_PAGEALLOC setting Joonsoo Kim
2016-02-04 8:32 ` Christian Borntraeger
2016-02-04 22:18 ` David Rientjes
2016-02-05 16:13 ` Joonsoo Kim
2016-02-04 5:56 ` [PATCH 2/5] mm/slub: " Joonsoo Kim
2016-02-04 8:31 ` Christian Borntraeger
2016-02-04 16:21 ` Joonsoo Kim
2016-02-04 5:56 ` [PATCH 3/5] sound: " Joonsoo Kim
2016-02-04 22:19 ` David Rientjes
2016-02-05 9:26 ` Takashi Iwai [this message]
2016-02-04 5:56 ` [PATCH 4/5] powerpc: " Joonsoo Kim
2016-02-04 22:22 ` David Rientjes
2016-02-04 5:56 ` [PATCH 5/5] tile: " Joonsoo Kim
2016-02-09 16:56 ` Chris Metcalf
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=s5hwpqj1p98.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=borntraeger@de.ibm.com \
--cc=cl@linux.com \
--cc=cmetcalf@ezchip.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=js1304@gmail.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.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