From: Laura Parkes <laura_parkes@btinternet.com>
To: "Greg Kroah-Hartman" <gregkh@suse.de>,
Andre Haupt <andre@bitwigglers.org>,
Andi Kleen <ak@linux.intel.com>, Peter Huewe <peterhuewe@gmx.de>,
"Kevin A. Granade" <kevin.granade@gmail.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [PATCH] Staging: asus_oled: fix spaces coding style in asus_oled.c
Date: Sat, 20 Mar 2010 19:03:31 +0000 [thread overview]
Message-ID: <201003201903.32025.laura_parkes@btinternet.com> (raw)
>From ada5a2f3c991cbbf8f6fbd97d72718c9bb806580 Mon Sep 17 00:00:00 2001
From: Laura Parkes <laura_parkes@btinternet.com>
Date: Sat, 20 Mar 2010 17:16:19 +0000
Subject: [PATCH] Staging: asus_oled: fix spaces coding style in asus_oled.c
This is a patch to the asus_oled.c file that fixes a spaces
warning found by checkpatch.pl tool.
Signed-off-by: Laura Parkes <laura_parkes@btinternet.com>
---
drivers/staging/asus_oled/asus_oled.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/staging/asus_oled/asus_oled.c b/drivers/staging/asus_oled/asus_oled.c
index 7ebecc9..9e7e677 100644
--- a/drivers/staging/asus_oled/asus_oled.c
+++ b/drivers/staging/asus_oled/asus_oled.c
@@ -771,7 +771,7 @@ static struct usb_driver oled_driver = {
};
static CLASS_ATTR_STRING(version, S_IRUGO,
- ASUS_OLED_UNDERSCORE_NAME " " ASUS_OLED_VERSION);
+ ASUS_OLED_UNDERSCORE_NAME " " ASUS_OLED_VERSION);
static int __init asus_oled_init(void)
{
--
1.6.3.3
next reply other threads:[~2010-03-20 19:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-20 19:03 Laura Parkes [this message]
2010-04-27 17:31 ` [PATCH] Staging: asus_oled: fix spaces coding style in asus_oled.c Greg KH
-- strict thread matches above, loose matches on Subject: below --
2010-04-13 18:44 Laura Parkes
2010-04-27 17:30 ` Greg KH
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=201003201903.32025.laura_parkes@btinternet.com \
--to=laura_parkes@btinternet.com \
--cc=ak@linux.intel.com \
--cc=andre@bitwigglers.org \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=kevin.granade@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
/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.