public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@lip6.fr>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: kbuild-all@01.org, Michael Halcrow <mhalcrow@google.com>,
	"Theodore Ts'o" <tytso@mit.edu>,
	Ildar Muslukhov <ildarm@google.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs crypto: fix semicolon.cocci warnings
Date: Wed, 17 Feb 2016 14:28:51 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.2.10.1602171428410.4547@hadrien> (raw)
In-Reply-To: <20160217185542.GA94388@jaegeuk.gateway>



On Wed, 17 Feb 2016, Jaegeuk Kim wrote:

> Hi Julia,
>
> I just submitted crypto patches, so if you don't mind, can I integrate your
> patches into my original ones?

No problem at all.

julia

>
> Thanks,
>
> On Wed, Feb 17, 2016 at 08:30:56AM -0500, Julia Lawall wrote:
> >  Remove unneeded semicolon.
> >
> > Generated by: scripts/coccinelle/misc/semicolon.cocci
> >
> > Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
> > Signed-off-by: Julia Lawall <julia.lawall@lip6.fr>
> > ---
> >
> >  crypto.c |    2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > --- a/fs/crypto/crypto.c
> > +++ b/fs/crypto/crypto.c
> > @@ -312,7 +312,7 @@ int fscrypt_zeroout_range(struct inode *
> >  		}
> >  		bio->bi_bdev = inode->i_sb->s_bdev;
> >  		bio->bi_iter.bi_sector =
> > -			pblk << (inode->i_sb->s_blocksize_bits - 9);;
> > +			pblk << (inode->i_sb->s_blocksize_bits - 9);
> >  		ret = bio_add_page(bio, ciphertext_page,
> >  					inode->i_sb->s_blocksize, 0);
> >  		if (ret != inode->i_sb->s_blocksize) {
>

      reply	other threads:[~2016-02-17 19:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-17 13:30 [PATCH] fs crypto: fix semicolon.cocci warnings Julia Lawall
2016-02-17 18:55 ` Jaegeuk Kim
2016-02-17 19:28   ` Julia Lawall [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=alpine.DEB.2.10.1602171428410.4547@hadrien \
    --to=julia.lawall@lip6.fr \
    --cc=ildarm@google.com \
    --cc=jaegeuk@kernel.org \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhalcrow@google.com \
    --cc=tytso@mit.edu \
    /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