cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] gfs2: removed unnecessary semicolon
Date: Fri, 4 Oct 2019 13:22:07 -0400 (EDT)	[thread overview]
Message-ID: <312248413.4882810.1570209727854.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1944905967.4863703.1570204154537.JavaMail.zimbra@redhat.com>

----- Original Message -----
> ----- Original Message -----
> > From: Aliasgar Surti <aliasgar.surti500@gmail.com>
> > 
> > There is use of unnecessary semicolon after switch case.
> > Removed the semicolon.
> > 
> > Signed-off-by: Aliasgar Surti <aliasgar.surti500@gmail.com>
> > ---
> >  fs/gfs2/recovery.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/fs/gfs2/recovery.c b/fs/gfs2/recovery.c
> > index c529f8749a89..f4aa8551277b 100644
> > --- a/fs/gfs2/recovery.c
> > +++ b/fs/gfs2/recovery.c
> > @@ -326,7 +326,7 @@ void gfs2_recover_func(struct work_struct *work)
> >  
> >  		default:
> >  			goto fail;
> > -		};
> > +		}
> >  
> >  		error = gfs2_glock_nq_init(ip->i_gl, LM_ST_SHARED,
> >  					   LM_FLAG_NOEXP | GL_NOCACHE, &ji_gh);
> > --
> > 2.17.1
> 
> Hi,
> 
> Thanks for the patch. I did a quick search and found two more:
> 
> glops.c-                break;
> glops.c:        };
> 
> inode.c-                        goto out_gunlock;
> inode.c:                };
> 
> Do you want to include those in your patch and re-submit it or
> should I cook up a second patch?

Hi,

I just went ahead and added the two above to your patch and pushed
it to for-next. Thanks.

Regards,

Bob Peterson



      reply	other threads:[~2019-10-04 17:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-02 17:46 [Cluster-devel] [PATCH] gfs2: removed unnecessary semicolon aliasgar.surti500
2019-10-04 15:49 ` Bob Peterson
2019-10-04 17:22   ` Bob Peterson [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=312248413.4882810.1570209727854.JavaMail.zimbra@redhat.com \
    --to=rpeterso@redhat.com \
    /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).