From: Sunny Kumar <sunny.kumar.roy@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: mdharm-usb@one-eyed-alien.net, gregkh@linuxfoundation.org,
linux-usb@vger.kernel.org, usb-storage@lists.one-eyed-alien.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] usb: storage : Remove c99 style commenting
Date: Fri, 26 Jun 2015 23:42:16 +0530 [thread overview]
Message-ID: <20150626181216.GA4775@sunny-DevBox> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1506261003260.1566-100000@iolanthe.rowland.org>
On Fri, Jun 26, 2015 at 10:08:42AM -0400, Alan Stern wrote:
> On Fri, 26 Jun 2015, Sunny Kumar wrote:
>
> > This patch fixes checkpatch.pl warning c99 style commenting.
> >
> > Signed-off-by: Sunny Kumar <sunny.kumar.roy@gmail.com>
> > ---
> > drivers/usb/storage/sddr55.c | 16 ++++++++--------
> > 1 file changed, 8 insertions(+), 8 deletions(-)
> >
> > diff --git a/drivers/usb/storage/sddr55.c b/drivers/usb/storage/sddr55.c
> > index aacedef..54d0a59 100644
> > --- a/drivers/usb/storage/sddr55.c
> > +++ b/drivers/usb/storage/sddr55.c
> > @@ -209,10 +209,10 @@ static int sddr55_read_data(struct us_data *us,
> > unsigned int len, offset;
> > struct scatterlist *sg;
> >
> > - // Since we only read in one block at a time, we have to create
> > - // a bounce buffer and move the data a piece at a time between the
> > - // bounce buffer and the actual transfer buffer.
> > -
> > + /* Since we only read in one block at a time, we have to create
> > + * a bounce buffer and move the data a piece at a time between the
> > + * bounce buffer and the actual transfer buffer.
> > + */
> > len = min((unsigned int) sectors, (unsigned int) info->blocksize >>
> > info->smallpageshift) * PAGESIZE;
> > buffer = kmalloc(len, GFP_NOIO);
> > @@ -336,10 +336,10 @@ static int sddr55_write_data(struct us_data *us,
> > return USB_STOR_TRANSPORT_FAILED;
> > }
> >
> > - // Since we only write one block at a time, we have to create
> > - // a bounce buffer and move the data a piece at a time between the
> > - // bounce buffer and the actual transfer buffer.
> > -
> > + /* Since we only write one block at a time, we have to create
> > + * a bounce buffer and move the data a piece at a time between the
> > + * bounce buffer and the actual transfer buffer.
> > + */
> > len = min((unsigned int) sectors, (unsigned int) info->blocksize >>
> > info->smallpageshift) * PAGESIZE;
> > buffer = kmalloc(len, GFP_NOIO);
>
> Why did you fix just these two sites? There are lots of other places
> in usb-storage that use C99-style comments:
>
> $ cd drivers/usb/storage
> $ egrep '[^:]//' *.[ch] | wc
> 177 1635 9562
>
> (The [^:] is to avoid matching things like "http://", and as a result
> this misses the four places where a // comment starts at the beginning
> of a line.)
>
> Why not fix all of them?
These were C99 muliline comments so thought of fixing ..
>
> Alan Stern
>
prev parent reply other threads:[~2015-06-26 18:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 6:14 [PATCH 1/1] usb: storage : Remove c99 style commenting Sunny Kumar
2015-06-26 12:33 ` Sergei Shtylyov
2015-06-26 14:08 ` Alan Stern
2015-06-26 18:12 ` Sunny Kumar [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=20150626181216.GA4775@sunny-DevBox \
--to=sunny.kumar.roy@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mdharm-usb@one-eyed-alien.net \
--cc=stern@rowland.harvard.edu \
--cc=usb-storage@lists.one-eyed-alien.net \
/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