From: Sasha Levin <sashal@kernel.org>
To: Nick Krause <xerofoify@gmail.com>, Joe Perches <joe@perches.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
josh@joshtriplett.org, robh@kernel.org, florian.vaussard@epfl.ch,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Checkpatch Feature Idea: Search directory for files with errors and warnings with -d argument
Date: Wed, 16 Jul 2014 22:53:43 -0400 [thread overview]
Message-ID: <53C73AB7.4080603@kernel.org> (raw)
In-Reply-To: <CAPDOMVgExn5i0ogz8dwtFgYXCPwGCpnt6Af_o-UOk-BUtFD9KA@mail.gmail.com>
On 07/16/2014 12:59 AM, Nick Krause wrote:
> On Wed, Jul 16, 2014 at 12:39 AM, Joe Perches <joe@perches.com> wrote:
>> > On Wed, 2014-07-16 at 00:28 -0400, Nick Krause wrote:
>>> >> I am cleaning up the kernel as it needs a lot of cleanup.
>> >
>> > Needs are curious things.
>> >
>> > Consistency is a nicety not really a need.
>> >
>> > Bugs need fixing. Defects need eliminating.
>> > Enhancements are appreciated. Inconsistent
>> > code style is a minor annoyance.
>> >
>> > I suggest you focus on the bugs, defects or
>> > enhancements in performance or testing.
>> >
>> > Are you really cross-compiling the patches you
>> > submit here or do you have an alpha on your desk?
>> >
>> >
> I am cross compiling then. I don't have the hardware :(.
Are you sure you're actually cross compiling them? From your
recent patchset it doesn't seem you even bother to do that:
diff --git a/arch/alpha/boot/misc.c b/arch/alpha/boot/misc.c
index 174b7c6..886e469 100644
--- a/arch/alpha/boot/misc.c
+++ b/arch/alpha/boot/misc.c
@@ -23,7 +23,7 @@
#include <asm/uaccess.h>
-#define memzero (s, n) memset((s), 0 , (n))
+#define memzero { (s, n) memset((s), 0 , (n)) }
#define puts srm_printk
extern long srm_printk(const char *, ...)
__attribute__ ((format (printf, 1, 2)));
@@ -61,8 +61,8 @@ static unsigned outcnt; /* bytes in output buffer */
/* Diagnostic functions */
#ifdef DEBUG
-# define Assert (cond, msg) {if (!(cond)) error(msg) ; }
-# define Trace(x) fprintf x
+# define Assert { (cond, msg) {if (!(cond)) error(msg) ; } }
+# define Trace { (x) fprintf x }
# define Tracev(x) {if (verbose) fprintf x ; }
# define Tracevv(x) {if (verbose > 1) fprintf x ; }
# define Tracec(c, x) {if (verbose && (c)) fprintf x ; }
Or:
diff --git a/arch/alpha/boot/misc.c b/arch/alpha/boot/misc.c
index 886e469..56c3325 100644
--- a/arch/alpha/boot/misc.c
+++ b/arch/alpha/boot/misc.c
@@ -144,7 +144,7 @@ static void error(char *x)
puts(x);
puts("\n\n -- System halted");
- while (1);
+ while{ (1); }
/* Halt */
}
Thanks,
Sasha
next prev parent reply other threads:[~2014-07-17 2:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 2:50 Checkpatch Feature Idea: Search directory for files with errors and warnings with -d argument Nick Krause
2014-07-16 3:38 ` Joe Perches
2014-07-16 4:16 ` Nick Krause
2014-07-16 4:23 ` Joe Perches
2014-07-16 4:28 ` Nick Krause
2014-07-16 4:39 ` Joe Perches
2014-07-16 4:59 ` Nick Krause
2014-07-17 2:53 ` Sasha Levin [this message]
2014-07-16 8:05 ` Theodore Ts'o
2014-07-16 13:08 ` Joe Perches
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=53C73AB7.4080603@kernel.org \
--to=sashal@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=florian.vaussard@epfl.ch \
--cc=joe@perches.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=xerofoify@gmail.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).