From: Dan Carpenter <dan.carpenter@oracle.com>
To: Luis de Bethencourt <luis@debethencourt.com>
Cc: m.chehab@samsung.com, devel@driverdev.osuosl.org,
gulsah.1004@gmail.com, gregkh@linuxfoundation.org,
jarod@wilsonet.com, linux-kernel@vger.kernel.org,
tuomas.tynkkynen@iki.fi, linux-media@vger.kernel.org
Subject: Re: [PATCH v3 2/2] staging: media: lirc: lirc_zilog.c: keep consistency in dev functions
Date: Fri, 5 Dec 2014 15:28:55 +0300 [thread overview]
Message-ID: <20141205122855.GD4912@mwanda> (raw)
In-Reply-To: <20141204223524.GA17650@biggie>
On Thu, Dec 04, 2014 at 10:35:24PM +0000, Luis de Bethencourt wrote:
> The previous patch switched some dev functions to move the string to a second
> line. Doing this for all similar functions because it makes the driver easier
> to read if all similar lines use the same criteria.
>
> Signed-off-by: Luis de Bethencourt <luis@debethencourt.com>
> ---
> drivers/staging/media/lirc/lirc_zilog.c | 155 +++++++++++++++++++++-----------
> 1 file changed, 102 insertions(+), 53 deletions(-)
>
> diff --git a/drivers/staging/media/lirc/lirc_zilog.c b/drivers/staging/media/lirc/lirc_zilog.c
> index 8814a7e..af46827 100644
> --- a/drivers/staging/media/lirc/lirc_zilog.c
> +++ b/drivers/staging/media/lirc/lirc_zilog.c
> @@ -322,7 +322,8 @@ static int add_to_buf(struct IR *ir)
> struct IR_tx *tx;
>
> if (lirc_buffer_full(rbuf)) {
> - dev_dbg(ir->l.dev, "buffer overflow\n");
> + dev_dbg(ir->l.dev,
> + "buffer overflow\n");
No. Don't do this. It's better if it is on one line.
regards,
dan carpenter
next prev parent reply other threads:[~2014-12-05 12:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 22:35 [PATCH v3 2/2] staging: media: lirc: lirc_zilog.c: keep consistency in dev functions Luis de Bethencourt
2014-12-05 12:28 ` Dan Carpenter [this message]
[not found] ` <CAPA4HGVhKuw6cQHMfRWrTLxd8u3P8a1noAPkzkgrFmsORgXUgw@mail.gmail.com>
2014-12-06 1:40 ` Mauro Carvalho Chehab
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=20141205122855.GD4912@mwanda \
--to=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=gulsah.1004@gmail.com \
--cc=jarod@wilsonet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=luis@debethencourt.com \
--cc=m.chehab@samsung.com \
--cc=tuomas.tynkkynen@iki.fi \
/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