Linux-Aspeed Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vijay Khemka <vijaykhemka@fb.com>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH] misc: aspeed-lpc-ctrl: Correct return values
Date: Thu, 24 Jan 2019 19:29:16 +0000	[thread overview]
Message-ID: <13C13AE8-63A4-4002-9E0D-70276C529448@fb.com> (raw)
In-Reply-To: <20190124081544.GA1649@kroah.com>



?On 1/24/19, 12:16 AM, "Greg Kroah-Hartman" <gregkh@linuxfoundation.org> wrote:

    On Wed, Jan 23, 2019 at 03:06:34PM -0800, Vijay Khemka wrote:
    > Corrected some of return values with appropriate meanings.
    > 
    > Signed-off-by: Vijay Khemka <vijaykhemka@fb.com>
    > ---
    >  drivers/misc/aspeed-lpc-ctrl.c | 15 +++++++--------
    >  1 file changed, 7 insertions(+), 8 deletions(-)
    > 
    > diff --git a/drivers/misc/aspeed-lpc-ctrl.c b/drivers/misc/aspeed-lpc-ctrl.c
    > index 332210e06e98..97ae341109d5 100644
    > --- a/drivers/misc/aspeed-lpc-ctrl.c
    > +++ b/drivers/misc/aspeed-lpc-ctrl.c
    > @@ -68,7 +68,6 @@ static long aspeed_lpc_ctrl_ioctl(struct file *file, unsigned int cmd,
    >  		unsigned long param)
    >  {
    >  	struct aspeed_lpc_ctrl *lpc_ctrl = file_aspeed_lpc_ctrl(file);
    > -	struct device *dev = file->private_data;
    >  	void __user *p = (void __user *)param;
    >  	struct aspeed_lpc_ctrl_mapping map;
    >  	u32 addr;
    > @@ -93,8 +92,8 @@ static long aspeed_lpc_ctrl_ioctl(struct file *file, unsigned int cmd,
    >  
    >  		/* If memory-region is not described in device tree */
    >  		if (!lpc_ctrl->mem_size) {
    > -			dev_err(dev, "Didn't find reserved memory\n");
    > -			return -EINVAL;
    > +			pr_err("aspeed_lpc_ctrl: ioctl: Didn't find reserved memory\n");
    
    Why did you change from dev_err() to pr_err()?  You just lost a lot of
    information that the user previously was getting from dev_err() :(

I did this as per review comment from Andrew Jeffery, as we don't want to put this error for driver. It has to be handled by userspace. But I am still reporting some error here.
    
    
    
    > +			return -ENXIO;
    >  		}
    >  
    >  		map.size = lpc_ctrl->mem_size;
    > @@ -134,16 +133,16 @@ static long aspeed_lpc_ctrl_ioctl(struct file *file, unsigned int cmd,
    >  
    >  		if (map.window_type == ASPEED_LPC_CTRL_WINDOW_FLASH) {
    >  			if (!lpc_ctrl->pnor_size) {
    > -				dev_err(dev, "Didn't find host pnor flash\n");
    > -				return -EINVAL;
    > +				pr_err("aspeed_lpc_ctrl: ioctl: Didn't find host pnor flash\n");
    
    Again, don't do that :(
    
    thanks,
    
    greg k-h
    


  reply	other threads:[~2019-01-24 19:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-23 23:06 [PATCH] misc: aspeed-lpc-ctrl: Correct return values Vijay Khemka
2019-01-24  8:15 ` Greg Kroah-Hartman
2019-01-24 19:29   ` Vijay Khemka [this message]
2019-02-11  5:22     ` Andrew Jeffery
2019-02-11 20:13       ` Vijay Khemka
  -- strict thread matches above, loose matches on Subject: below --
2019-05-01 22:38 Vijay Khemka
2019-05-02  6:40 ` Greg Kroah-Hartman
2019-05-02  6:49   ` Andrew Jeffery
2019-05-03 17:55     ` Vijay Khemka

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=13C13AE8-63A4-4002-9E0D-70276C529448@fb.com \
    --to=vijaykhemka@fb.com \
    --cc=linux-aspeed@lists.ozlabs.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