All of lore.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown@intel.com>
To: akpm@osdl.org
Cc: linux-acpi@vger.kernel.org, adobriyan@gmail.com
Subject: Re: [patch 06/12] asus_acpi: don't printk on writing garbage to proc files
Date: Sat, 14 Oct 2006 04:07:45 -0400	[thread overview]
Message-ID: <200610140407.45983.len.brown@intel.com> (raw)
In-Reply-To: <200610102120.k9ALKa9G024281@shell0.pdx.osdl.net>

Applied.

thanks,
-Len

On Tuesday 10 October 2006 17:20, akpm@osdl.org wrote:
> From: Alexey Dobriyan <adobriyan@gmail.com>
> 
> * This reporting is useless (you get errno anyway).
> * This reporting is already inconsistent in driver.
> * Looks like created files in proc are rw-rw-rw- by default.
> 
> Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
> Signed-off-by: Andrew Morton <akpm@osdl.org>
> ---
> 
>  drivers/acpi/asus_acpi.c |   10 +---------
>  1 files changed, 1 insertion(+), 9 deletions(-)
> 
> diff -puN drivers/acpi/asus_acpi.c~asus_acpi-dont-printk-on-writing-garbage-to-proc-files drivers/acpi/asus_acpi.c
> --- a/drivers/acpi/asus_acpi.c~asus_acpi-dont-printk-on-writing-garbage-to-proc-files
> +++ a/drivers/acpi/asus_acpi.c
> @@ -629,9 +629,7 @@ proc_write_ledd(struct file *file, const
>  			       "Asus ACPI: LED display write failed\n");
>  		else
>  			hotk->ledd_status = (u32) value;
> -	} else if (rv < 0)
> -		printk(KERN_WARNING "Asus ACPI: Error reading user input\n");
> -
> +	}
>  	return rv;
>  }
>  
> @@ -849,10 +847,7 @@ proc_write_brn(struct file *file, const 
>  		value = (0 < value) ? ((15 < value) ? 15 : value) : 0;
>  		/* 0 <= value <= 15 */
>  		set_brightness(value);
> -	} else if (rv < 0) {
> -		printk(KERN_WARNING "Asus ACPI: Error reading user input\n");
>  	}
> -
>  	return rv;
>  }
>  
> @@ -897,9 +892,6 @@ proc_write_disp(struct file *file, const
>  	rv = parse_arg(buffer, count, &value);
>  	if (rv > 0)
>  		set_display(value);
> -	else if (rv < 0)
> -		printk(KERN_WARNING "Asus ACPI: Error reading user input\n");
> -
>  	return rv;
>  }
>  
> _
> -
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

      reply	other threads:[~2006-10-14  8:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-10 21:20 [patch 06/12] asus_acpi: don't printk on writing garbage to proc files akpm
2006-10-14  8:07 ` Len Brown [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=200610140407.45983.len.brown@intel.com \
    --to=len.brown@intel.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@osdl.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.