From: eddi1983 <eddi1983@gmx.net>
To: mchehab@kernel.org
Cc: gregkh@linuxfoundation.org, diaconitatamara@gmail.com,
daniel.baluta@gmail.com, eraretuya@gmail.com,
elise.lennion@gmail.com, linux-media@vger.kernel.org,
0devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Christoph Fanelsa <eddi1983@gmx.net>
Subject: [PATCH] staging: media: cxd2099: Fix checkpatch issues
Date: Tue, 16 May 2017 22:07:40 +0200 [thread overview]
Message-ID: <20170516200740.27692-1-eddi1983@gmx.net> (raw)
From: Christoph Fanelsa <eddi1983@gmx.net>
Fix checkpatch warnings of prefered using '%s..", __func__' as function name in a string
Signed-off-by: Christoph Fanelsa <eddi1983@gmx.net>
---
drivers/staging/media/cxd2099/cxd2099.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/media/cxd2099/cxd2099.c b/drivers/staging/media/cxd2099/cxd2099.c
index 18186d0fa1a6..370ecb959543 100644
--- a/drivers/staging/media/cxd2099/cxd2099.c
+++ b/drivers/staging/media/cxd2099/cxd2099.c
@@ -473,7 +473,7 @@ static int slot_shutdown(struct dvb_ca_en50221 *ca, int slot)
{
struct cxd *ci = ca->data;
- dev_info(&ci->i2c->dev, "slot_shutdown\n");
+ dev_info(&ci->i2c->dev, "%s\n", __func__);
mutex_lock(&ci->lock);
write_regm(ci, 0x09, 0x08, 0x08);
write_regm(ci, 0x20, 0x80, 0x80); /* Reset CAM Mode */
@@ -564,7 +564,7 @@ static int read_data(struct dvb_ca_en50221 *ca, int slot, u8 *ebuf, int ecount)
campoll(ci);
mutex_unlock(&ci->lock);
- dev_info(&ci->i2c->dev, "read_data\n");
+ dev_info(&ci->i2c->dev, "%s\n", __func__);
if (!ci->dr)
return 0;
@@ -584,7 +584,7 @@ static int write_data(struct dvb_ca_en50221 *ca, int slot, u8 *ebuf, int ecount)
struct cxd *ci = ca->data;
mutex_lock(&ci->lock);
- dev_info(&ci->i2c->dev, "write_data %d\n", ecount);
+ dev_info(&ci->i2c->dev, "%s %d\n", __func__, ecount);
write_reg(ci, 0x0d, ecount >> 8);
write_reg(ci, 0x0e, ecount & 0xff);
write_block(ci, 0x11, ebuf, ecount);
--
2.13.0
next reply other threads:[~2017-05-16 20:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 20:07 eddi1983 [this message]
2017-05-16 20:47 ` Jasmin J.
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=20170516200740.27692-1-eddi1983@gmx.net \
--to=eddi1983@gmx.net \
--cc=0devel@driverdev.osuosl.org \
--cc=daniel.baluta@gmail.com \
--cc=diaconitatamara@gmail.com \
--cc=elise.lennion@gmail.com \
--cc=eraretuya@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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 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®