From: Curtis McEnroe <programble@gmail.com>
To: gregkh@suse.de
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Curtis McEnroe <programble@gmail.com>
Subject: [PATCH 3/5] [media] tm6000: Cleaned up code style in tm6000-i2c.c
Date: Thu, 2 Jun 2011 20:33:32 -0400 [thread overview]
Message-ID: <1307061214-14837-2-git-send-email-programble@gmail.com> (raw)
In-Reply-To: <1307061214-14837-1-git-send-email-programble@gmail.com>
Replaced __FUNCTION__ with __func__
Signed-off-by: Curtis McEnroe <programble@gmail.com>
---
drivers/staging/tm6000/tm6000-i2c.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/staging/tm6000/tm6000-i2c.c b/drivers/staging/tm6000/tm6000-i2c.c
index 8828c12..5a651ea 100644
--- a/drivers/staging/tm6000/tm6000-i2c.c
+++ b/drivers/staging/tm6000/tm6000-i2c.c
@@ -40,7 +40,7 @@ MODULE_PARM_DESC(i2c_debug, "enable debug messages [i2c]");
#define i2c_dprintk(lvl, fmt, args...) if (i2c_debug >= lvl) do { \
printk(KERN_DEBUG "%s at %s: " fmt, \
- dev->name, __FUNCTION__ , ##args); } while (0)
+ dev->name, __func__, ##args); } while (0)
static int tm6000_i2c_send_regs(struct tm6000_core *dev, unsigned char addr,
__u8 reg, char *buf, int len)
--
1.7.5.2
next prev parent reply other threads:[~2011-06-03 0:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 0:33 [PATCH 2/5] [media] tm6000: Cleaned up code style in tm6000-dbv.c Curtis McEnroe
2011-06-03 0:33 ` Curtis McEnroe [this message]
2011-06-03 0:33 ` [PATCH 4/5] [media] tm6000: Clean up code style in tm6000-input.c Curtis McEnroe
2011-06-03 0:33 ` [PATCH 5/5] [media] tm6000: Cleaned up code style in tm6000-alsa.c Curtis McEnroe
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=1307061214-14837-2-git-send-email-programble@gmail.com \
--to=programble@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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.