From: David Dillow <dave@thedillows.org>
To: Jaswinder Singh <jaswinder@infradead.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL]: firmware patches for building firmware into kernel
Date: Fri, 08 Aug 2008 08:36:42 -0400 [thread overview]
Message-ID: <1218199002.17642.59.camel@obelisk.thedillows.org> (raw)
In-Reply-To: <1218170004.2540.28.camel@jaswinder.satnam>
On Fri, 2008-08-08 at 10:03 +0530, Jaswinder Singh wrote:
> On Fri, 2008-08-08 at 00:10 -0400, David Dillow wrote:
>
> > I'll take a closer look when I'm awake, but there are some nitpicky
> > style issues remaining:
>
> Please give me your script I will try with your scripts.
I am afraid I can send you neither my eyes nor my gray matter. Loaning
the use of them is another matter, but you've had them at least
semi-engaged for some time now. :)
The things I'm pointing out may be nitpicky, yes, but they are things
you get from looking at the shape of the code and seeing ways that it
could be made simpler and more readable.
> > You don't need the 'goto out', a break will work fine.
>
> Earlier I was also using break.
> For a safe side I used goto as If some one write more code it will not
> make any problem.
So the person who adds more code can change to a goto at that time --
meanwhile, the code will be more readable.
> > And you'll not be
> > pressed up against the right side of the screen if you just do
>
> Yes, I also think about this. But this is not an issue as it is < 80
> and every thing is coming in one line only.
Is the wrapping on the printk not just butt-ugly to you? If it can be
easily avoided by removing some indent, why wouldn't you want to?
These are small points, to be sure.
Dave
prev parent reply other threads:[~2008-08-08 12:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 16:56 Jaswinder Singh
2008-08-07 17:30 ` David Dillow
2008-08-07 17:34 ` Jaswinder Singh
2008-08-07 18:21 ` David Dillow
2008-08-08 1:38 ` Jaswinder Singh
2008-08-08 2:59 ` David Dillow
2008-08-08 3:39 ` Jaswinder Singh
2008-08-08 4:25 ` David Dillow
2008-08-08 6:08 ` Jaswinder Singh
2008-08-08 3:31 ` Jaswinder Singh
2008-08-08 4:10 ` David Dillow
2008-08-08 4:33 ` Jaswinder Singh
2008-08-08 12:36 ` David Dillow [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=1218199002.17642.59.camel@obelisk.thedillows.org \
--to=dave@thedillows.org \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dwmw2@infradead.org \
--cc=jaswinder@infradead.org \
--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®