From: Joe Perches <joe@perches.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Keerthimai Janarthanan <keerthimaipb@gmail.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] staging :keucr:scsiglue.c : fixed a macros should not be colon terminated issue
Date: Tue, 04 Mar 2014 17:44:01 -0800 [thread overview]
Message-ID: <1393983841.3271.19.camel@joe-AO722> (raw)
In-Reply-To: <20140305011054.GA10990@kroah.com>
On Tue, 2014-03-04 at 17:10 -0800, Greg KH wrote:
> On Sun, Mar 02, 2014 at 06:21:16PM +0530, Keerthimai Janarthanan wrote:
> > fixed a coding style issue.
[]
> > diff --git a/drivers/staging/keucr/scsiglue.c b/drivers/staging/keucr/scsiglue.c
[]
> > @@ -277,7 +277,7 @@ static int show_info(struct seq_file *m, struct Scsi_Host *host)
> > do { \
> > if (us->fflags & value) \
> > SPRINTF(" " #name); \
> > - } while (0);
> > + } while (0)
>
> You just broke the build.
>
> Please ALWAYS test your patches, don't break someone else's build with
> broken patches...
>
> Please be more careful.
Thanks Greg.
Keerthimai, a possibly "better" fix would be to add a
do { ... } while (0) guard and semicolons to the relatively
ugly US_DO_ALL_FLAGS macro and US_FLAG uses in
include/linux/usb_usual.h
include/linux/usb_usual.h:#define US_DO_ALL_FLAGS \
include/linux/usb_usual.h- US_FLAG(SINGLE_LUN, 0x00000001) \
include/linux/usb_usual.h- /* allow access to only LUN 0 */ \
include/linux/usb_usual.h- US_FLAG(NEED_OVERRIDE, 0x00000002) \
include/linux/usb_usual.h- /* unusual_devs entry is necessary */ \
...
and then add a semicolon to the uses of US_DO_ALL_FLAGS
and then remove a semicolon as above.
prev parent reply other threads:[~2014-03-05 1:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-02 12:51 Keerthimai Janarthanan
2014-03-05 1:10 ` Greg KH
2014-03-05 1:44 ` Joe Perches [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=1393983841.3271.19.camel@joe-AO722 \
--to=joe@perches.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=keerthimaipb@gmail.com \
--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®