From: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/4] x86: coding style fixes in arch/x86/pci/
Date: Wed, 9 Jan 2008 00:30:32 +0100 [thread overview]
Message-ID: <20080109003032.78cfeedd@paolo-desktop> (raw)
Hi Ingo,
after you asked me to work against x86.git[1] I noticed
that 4 out of 5 of my previous patches didn't make sense any longer.
While I was compiling the kernel, and hopefully starting doing something
more useful (Sam, again thank you for the hints),
I create these 4 very simple patches fixing some coding style issue.
[PATCH 1/4] x86: coding style fixes in /arch/x86/pci/common.c
[PATCH 2/4] x86: coding style fixes in arch/x86/pci/acpi.c
[PATCH 3/4] x86: coding style fixes in arch/x86/pci/direct.c
[PATCH 4/4] x86: coding style fixes in arch/x86/pci/fixup.c
And here is the diffstat:
arch/x86/pci/acpi.c | 4 ++--
arch/x86/pci/common.c | 12 +++++-------
arch/x86/pci/direct.c | 10 +++++-----
arch/x86/pci/fixup.c | 30 +++++++++++++++---------------
4 files changed, 27 insertions(+), 29 deletions(-)
[1] git-pull git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86.git mm
reply other threads:[~2008-01-08 23:30 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=20080109003032.78cfeedd@paolo-desktop \
--to=paolo.ciarrocchi@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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