From: Angus Hammond <angusgh@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Subject: [PATCH] Fixed coding style in drivers/acpi/ac.c
Date: Mon, 18 Jul 2011 18:14:20 +0100 [thread overview]
Message-ID: <4e246fa2.c7cde30a.3423.5570@mx.google.com> (raw)
Changed lines causing errors from scrips/checkpatch.pl.
---
drivers/acpi/ac.c | 18 +++++++++---------
1 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/acpi/ac.c b/drivers/acpi/ac.c
index 58c3f74..e510828 100644
--- a/drivers/acpi/ac.c
+++ b/drivers/acpi/ac.c
@@ -1,5 +1,5 @@
/*
- * acpi_ac.c - ACPI AC Adapter Driver ($Revision: 27 $)
+ * acpi_ac.c - ACPI AC Adapter Driver
*
* Copyright (C) 2001, 2002 Andy Grover <andrew.grover@intel.com>
* Copyright (C) 2001, 2002 Paul Diefenbaugh <paul.s.diefenbaugh@intel.com>
@@ -54,8 +54,8 @@ MODULE_DESCRIPTION("ACPI AC Adapter Driver");
MODULE_LICENSE("GPL");
#ifdef CONFIG_ACPI_PROCFS_POWER
-extern struct proc_dir_entry *acpi_lock_ac_dir(void);
-extern void *acpi_unlock_ac_dir(struct proc_dir_entry *acpi_ac_dir);
+struct proc_dir_entry *acpi_lock_ac_dir(void);
+void *acpi_unlock_ac_dir(struct proc_dir_entry *acpi_ac_dir);
static int acpi_ac_open_fs(struct inode *inode, struct file *file);
#endif
@@ -85,7 +85,7 @@ static struct acpi_driver acpi_ac_driver = {
struct acpi_ac {
struct power_supply charger;
- struct acpi_device * device;
+ struct acpi_device *device;
unsigned long long state;
};
@@ -102,7 +102,7 @@ static const struct file_operations acpi_ac_fops = {
#endif
/* --------------------------------------------------------------------------
- AC Adapter Management
+ AC Adapter Management
-------------------------------------------------------------------------- */
static int acpi_ac_get_state(struct acpi_ac *ac)
@@ -124,7 +124,7 @@ static int acpi_ac_get_state(struct acpi_ac *ac)
}
/* --------------------------------------------------------------------------
- sysfs I/F
+ sysfs I/F
-------------------------------------------------------------------------- */
static int get_ac_property(struct power_supply *psy,
enum power_supply_property psp,
@@ -154,7 +154,7 @@ static enum power_supply_property ac_props[] = {
#ifdef CONFIG_ACPI_PROCFS_POWER
/* --------------------------------------------------------------------------
- FS Interface (/proc)
+ FS Interface (/proc)
-------------------------------------------------------------------------- */
static struct proc_dir_entry *acpi_ac_dir;
@@ -230,7 +230,7 @@ static int acpi_ac_remove_fs(struct acpi_device *device)
#endif
/* --------------------------------------------------------------------------
- Driver Model
+ Driver Model
-------------------------------------------------------------------------- */
static void acpi_ac_notify(struct acpi_device *device, u32 event)
@@ -298,7 +298,7 @@ static int acpi_ac_add(struct acpi_device *device)
acpi_device_name(device), acpi_device_bid(device),
ac->state ? "on-line" : "off-line");
- end:
+end:
if (result) {
#ifdef CONFIG_ACPI_PROCFS_POWER
acpi_ac_remove_fs(device);
--
1.7.4.1
next reply other threads:[~2011-07-18 17:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-18 17:14 Angus Hammond [this message]
2011-07-18 17:52 ` [PATCH] Fixed coding style in drivers/acpi/ac.c Joe Perches
-- strict thread matches above, loose matches on Subject: below --
2011-06-22 21:14 Angus Hammond
2011-06-22 21:14 Angus Hammond
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=4e246fa2.c7cde30a.3423.5570@mx.google.com \
--to=angusgh@gmail.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 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.