mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] block: wrong return value
Date: Thu, 23 Oct 2014 21:58:59 +0530	[thread overview]
Message-ID: <20141023162859.GB6590@sudip-PC> (raw)
In-Reply-To: <54492840.9050704@kernel.dk>

On Thu, Oct 23, 2014 at 10:09:36AM -0600, Jens Axboe wrote:
> On 10/23/2014 10:04 AM, Sudip Mukherjee wrote:
> > while compiling integer err was showing as a set but unused variable.
> > elevator_init_fn can be either cfq_init_queue or deadline_init_queue
> > or noop_init_queue.
> > all three of these functions are returning -ENOMEM if they fail to
> > allocate the queue.
> > so we should actually be returning the error code rather than
> > returning 0 always.
> > 
> > Signed-off-by: Sudip Mukherjee <sudip@vectorindia.org>
> > ---
> > 
> > change in v2: added elevator_put
> > 
> >  block/elevator.c | 6 ++++--
> >  1 file changed, 4 insertions(+), 2 deletions(-)
> > 
> > diff --git a/block/elevator.c b/block/elevator.c
> > index 24c28b6..1267c2b 100644
> > --- a/block/elevator.c
> > +++ b/block/elevator.c
> > @@ -184,7 +184,7 @@ static void elevator_release(struct kobject *kobj)
> >  int elevator_init(struct request_queue *q, char *name)
> >  {
> >  	struct elevator_type *e = NULL;
> > -	int err;
> > +	int err = 0;
> 
> Why init it to 0?
not required actually. my initial thinking was that we are returning 0 on success or else the error code. so gave it a default value of 0.
but elevator_init_fn is returning 0 on success , so we will get 0 even if we do not initialize it.
should i resend after modifying it?

thanks
sudip
> 
> -- 
> Jens Axboe
> 

  reply	other threads:[~2014-10-23 16:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-23 16:04 Sudip Mukherjee
2014-10-23 16:09 ` Jens Axboe
2014-10-23 16:28   ` Sudip Mukherjee [this message]
2014-10-23 16:30     ` Jens Axboe

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=20141023162859.GB6590@sudip-PC \
    --to=sudipm.mukherjee@gmail.com \
    --cc=axboe@kernel.dk \
    --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

all inboxes | Powered by JetHome®