From: "ira.weiny" <ira.weiny@intel.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: devel@driverdev.osuosl.org, gregkh@linuxfoundation.org,
dledford@redhat.com, dennis.dalessandro@intel.com,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH 4/8] staging/rdma/hfi1: remove unneeded goto done
Date: Wed, 11 Nov 2015 10:15:53 -0500 [thread overview]
Message-ID: <20151111151552.GA13414@phlsvsds.ph.intel.com> (raw)
In-Reply-To: <20151111090108.GB18797@mwanda>
On Wed, Nov 11, 2015 at 12:01:08PM +0300, Dan Carpenter wrote:
> On Wed, Nov 11, 2015 at 12:43:05AM -0500, ira.weiny@intel.com wrote:
> > From: Ira Weiny <ira.weiny@intel.com>
> >
> > This goto done is followed by an if (ret) break in the outer switch clause. It
> > is unnecessary.
> >
> > Signed-off-by: Dennis Dalessandro <dennis.dalessandro@intel.com>
> > Signed-off-by: Ira Weiny <ira.weiny@intel.com>
> > ---
> > drivers/staging/rdma/hfi1/diag.c | 3 +--
> > 1 file changed, 1 insertion(+), 2 deletions(-)
> >
> > diff --git a/drivers/staging/rdma/hfi1/diag.c b/drivers/staging/rdma/hfi1/diag.c
> > index 2bb857b2a103..556a47591989 100644
> > --- a/drivers/staging/rdma/hfi1/diag.c
> > +++ b/drivers/staging/rdma/hfi1/diag.c
> > @@ -1053,7 +1053,6 @@ static long hfi1_ioctl(struct file *fp, unsigned int cmd, unsigned long arg)
> > break;
> > default:
> > ret = -EINVAL;
> > - goto done;
> > }
> > ret = set_link_state(ppd, dev_state);
> > break;
>
> Wut? No it's not.
Sorry, you are correct at this point in the series.
I got over zealous with my splitting of this patch. This needs to be squashed
into
staging/rdma/hfi1: Return immediately on error
Which returns here.
Ira
next prev parent reply other threads:[~2015-11-11 15:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 5:43 [PATCH 0/8] Fix hfi1_ioctl locking ira.weiny-ral2JQCrhuEAvxtiuMwx3w
[not found] ` <1447220589-9067-1-git-send-email-ira.weiny-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-11-11 5:43 ` [PATCH 1/8] staging/rdma/hfi1: diag.c Correct code style issues ira.weiny-ral2JQCrhuEAvxtiuMwx3w
2015-11-11 5:43 ` [PATCH 5/8] staging/rdma/hfi1: return early if setlink state was specified ira.weiny-ral2JQCrhuEAvxtiuMwx3w
2015-11-11 9:06 ` Dan Carpenter
2015-11-11 5:43 ` [PATCH 6/8] staging/rdma/hfi1: Further clean up hfi1_ioctl parameter checks ira.weiny-ral2JQCrhuEAvxtiuMwx3w
2015-11-11 5:43 ` [PATCH 8/8] staging/rdma/hfi1: Return immediately on error ira.weiny-ral2JQCrhuEAvxtiuMwx3w
2015-11-11 5:43 ` [PATCH 2/8] staging/rdma/hfi1: Fix camel case variables ira.weiny
2015-11-11 5:43 ` [PATCH 3/8] staging/rdma/hfi1: Return early from hfi1_ioctl parameter errors ira.weiny
2015-11-11 5:43 ` [PATCH 4/8] staging/rdma/hfi1: remove unneeded goto done ira.weiny
[not found] ` <1447220589-9067-5-git-send-email-ira.weiny-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-11-11 9:01 ` Dan Carpenter
2015-11-11 15:15 ` ira.weiny [this message]
2015-11-11 9:03 ` Dan Carpenter
2015-11-11 14:00 ` Dennis Dalessandro
2015-11-11 5:43 ` [PATCH 7/8] staging/rdma/hfi1: Reduce snoop locking scope in IOCTL handler ira.weiny
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=20151111151552.GA13414@phlsvsds.ph.intel.com \
--to=ira.weiny@intel.com \
--cc=dan.carpenter@oracle.com \
--cc=dennis.dalessandro@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=dledford@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-rdma@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).