From: Aron Griffis <aron@hp.com>
To: linux-ia64@vger.kernel.org
Subject: [PATCH 0 of 4] cleanups for efi.c
Date: Wed, 12 Dec 2007 15:07:47 +0000 [thread overview]
Message-ID: <patchbomb.1197472067@jenkins.nashua> (raw)
These trivial patches clean up efi.c. There are no functionality
changes introduced by these patches.
1/4 - fix whitespace, fit in 80 columns, repair some indentation
2/4 - spelling and punctuation
3/4 - add /* never reached */ to a couple returns
4/4 - use a #define to reduce code duplication
Of these, I only intended to create 1/4, the others were just
byproducts... In particular, I'm ambivalent about 4/4. It reduces
code duplication and makes things easier to read, but does so by
introducing a #define, so it's a bit of a toss-up.
Aron
reply other threads:[~2007-12-12 15:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=patchbomb.1197472067@jenkins.nashua \
--to=aron@hp.com \
--cc=linux-ia64@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.