From: Matthias Schid <aircrach115@gmail.com>
To: gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, sjakub@gmail.com,
jonbrett.dev@gmail.com, cruz@massive-dynamics.biz,
joe@perches.com, devel@driverdev.osuosl.org,
linux-kernel@i4.cs.fau.de, steffhip@googlemail.com,
simon.puels@gmail.com, Matthias Schid <aircrach115@gmail.com>
Subject: [PATCH 1/2] staging/asus_oled fixed alignment in defines
Date: Wed, 5 Jun 2013 12:50:44 +0200 [thread overview]
Message-ID: <1370429445-17185-2-git-send-email-aircrach115@gmail.com> (raw)
In-Reply-To: <1370429445-17185-1-git-send-email-aircrach115@gmail.com>
replaced spaces in incorrect alignment in defines with tabs
Signed-off-by: Matthias Schid <aircrach115@gmail.com>
Signed-off-by: Stefan Huber <steffhip@googlemail.com>
Signed-off-by: Simon Puels <simon.puels@gmail.com>
---
drivers/staging/asus_oled/asus_oled.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/asus_oled/asus_oled.c b/drivers/staging/asus_oled/asus_oled.c
index 4598a2f..173fb9a 100644
--- a/drivers/staging/asus_oled/asus_oled.c
+++ b/drivers/staging/asus_oled/asus_oled.c
@@ -50,9 +50,9 @@
#define ASUS_OLED_DISP_HEIGHT 32
#define ASUS_OLED_PACKET_BUF_SIZE 256
-#define USB_VENDOR_ID_ASUS 0x0b05
-#define USB_DEVICE_ID_ASUS_LCM 0x1726
-#define USB_DEVICE_ID_ASUS_LCM2 0x175b
+#define USB_VENDOR_ID_ASUS 0x0b05
+#define USB_DEVICE_ID_ASUS_LCM 0x1726
+#define USB_DEVICE_ID_ASUS_LCM2 0x175b
MODULE_AUTHOR("Jakub Schmidtke, sjakub@gmail.com");
MODULE_DESCRIPTION("Asus OLED Driver");
--
1.7.10.4
next prev parent reply other threads:[~2013-06-05 11:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 10:50 [PATCH 0/2] staging/asus_oled fixed style issues Matthias Schid
2013-06-05 10:50 ` Matthias Schid [this message]
2013-06-05 10:50 ` [PATCH 2/2] staging/asus_oled fixed linebreak style issue Matthias Schid
2013-06-05 11:15 ` Dan Carpenter
2013-06-05 12:04 ` [PATCH 2/2] staging/asus_oled fixed linebreak and printk issue Matthias Schid
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=1370429445-17185-2-git-send-email-aircrach115@gmail.com \
--to=aircrach115@gmail.com \
--cc=cruz@massive-dynamics.biz \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=jonbrett.dev@gmail.com \
--cc=linux-kernel@i4.cs.fau.de \
--cc=linux-kernel@vger.kernel.org \
--cc=simon.puels@gmail.com \
--cc=sjakub@gmail.com \
--cc=steffhip@googlemail.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
all inboxes | Powered by JetHome®