linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Dooks <ben-linux@fluff.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Ben Dooks <ben-linux@fluff.org>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] input: Tone down logging from S3C touchscreen driver
Date: Tue, 1 Jun 2010 00:19:58 +0100	[thread overview]
Message-ID: <20100531231958.GS4720@trinity.fluff.org> (raw)
In-Reply-To: <1275328371-32066-1-git-send-email-broonie@opensource.wolfsonmicro.com>

On Mon, May 31, 2010 at 06:52:51PM +0100, Mark Brown wrote:
> The S3C touchscreen driver is logging at LOG_INFO on every stylus up
> event which spams the console needlessly.  Reduce the priority of the
> message to debug level for some peace and quiet.
> 
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Acekd-by: Ben Dooks <ben-linux@fluff.org>
> ---
>  drivers/input/touchscreen/s3c2410_ts.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/input/touchscreen/s3c2410_ts.c b/drivers/input/touchscreen/s3c2410_ts.c
> index ac5d0f9..6085d12 100644
> --- a/drivers/input/touchscreen/s3c2410_ts.c
> +++ b/drivers/input/touchscreen/s3c2410_ts.c
> @@ -173,7 +173,7 @@ static irqreturn_t stylus_irq(int irq, void *dev_id)
>  	if (down)
>  		s3c_adc_start(ts.client, 0, 1 << ts.shift);
>  	else
> -		dev_info(ts.dev, "%s: count=%d\n", __func__, ts.count);
> +		dev_dbg(ts.dev, "%s: count=%d\n", __func__, ts.count);
>  
>  	if (ts.features & FEAT_PEN_IRQ) {
>  		/* Clear pen down/up interrupt */
> -- 
> 1.7.1
> 

-- 
-- 
Ben

Q:      What's a light-year?
A:      One-third less calories than a regular year.


      parent reply	other threads:[~2010-05-31 23:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-31 17:52 [PATCH] input: Tone down logging from S3C touchscreen driver Mark Brown
2010-05-31 19:03 ` Dmitry Torokhov
2010-05-31 23:19 ` Ben Dooks [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=20100531231958.GS4720@trinity.fluff.org \
    --to=ben-linux@fluff.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).