From: Joe Perches <joe@perches.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org, pierre@ossman.eu,
swetland@google.com, Andrew Morton <akpm@linux-foundation.org>,
San Mehat <san@google.com>
Subject: [PATCH V2 0/3] msm_sdcc: cleanups
Date: Tue, 30 Jun 2009 08:31:36 -0700 [thread overview]
Message-ID: <cover.1246371533.git.joe@perches.com> (raw)
In-Reply-To: <20090630132112.GB28447@elf.ucw.cz>
Hi Pavel.
Here's another slightly redone pass with your compile fixes.
In patch 3/3 I changed the argument list of handle_irq_data
for a bit better localization of variable use.
Joe Perches (3):
msm_sdcc.c: Convert printk(KERN_<level> to pr_<level>(
msm_sdcc.c: stylistic cleaning
msm_sdcc.c: Move overly indented code to separate function
drivers/mmc/host/msm_sdcc.c | 282 ++++++++++++++++++++----------------------
1 files changed, 134 insertions(+), 148 deletions(-)
next prev parent reply other threads:[~2009-06-30 15:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 21:41 MMC driver for HTC Dream Pavel Machek
2009-06-29 21:46 ` Brian Swetland
2009-06-29 22:16 ` Pavel Machek
2009-06-30 0:02 ` [PATCH 0/3] msm_sdcc: A few more cleanups Joe Perches
2009-06-30 0:02 ` [PATCH 1/3] msm_sdcc.c: Convert printk(KERN_<level> to pr_<level>( Joe Perches
2009-06-30 0:02 ` [PATCH 2/3] msm_sdcc.c: stylistic cleaning Joe Perches
2009-06-30 0:02 ` [PATCH 3/3] msm_sdcc.c: Move overly indented code to separate function Joe Perches
2009-06-30 6:57 ` [PATCH 0/3] msm_sdcc: A few more cleanups Pavel Machek
2009-06-30 12:30 ` Joe Perches
2009-06-30 13:21 ` Pavel Machek
2009-06-30 15:31 ` Joe Perches [this message]
2009-06-30 15:31 ` [PATCH V2 1/3] msm_sdcc.c: Convert printk(KERN_<level> to pr_<level>( Joe Perches
2009-06-30 15:31 ` [PATCH V2 2/3] msm_sdcc.c: stylistic cleaning Joe Perches
2009-06-30 15:31 ` [PATCH V2 3/3] msm_sdcc.c: Move overly indented code to separate function 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=cover.1246371533.git.joe@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=pierre@ossman.eu \
--cc=san@google.com \
--cc=swetland@google.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