From: Dan Carpenter <dan.carpenter@oracle.com>
To: "Mathieu Rhéaume" <mathieu@codingrhemes.com>
Cc: devel@driverdev.osuosl.org, gregkh@linuxfoundation.org,
serban.constantinescu@arm.com, linux-kernel@vger.kernel.org,
arve@android.com, mirsal@mirsal.fr
Subject: Re: [PATCH] Staging : android: binder.c: Prefer seq_puts to seq_printf
Date: Wed, 2 Oct 2013 10:55:39 +0300 [thread overview]
Message-ID: <20131002075539.GV6192@mwanda> (raw)
In-Reply-To: <1380679056-10175-1-git-send-email-mathieu@codingrhemes.com>
On Tue, Oct 01, 2013 at 09:57:36PM -0400, Mathieu Rhéaume wrote:
> This patch changes seq_printf for seq_puts in binder.c.
> It fixes the warnings emitted by checkpatch.pl.
Which warnings? Seems like a false positive somehow because seq_puts()
is totally wrong here. This doesn't compile.
regards,
dan carpenter
prev parent reply other threads:[~2013-10-02 7:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-02 1:57 [PATCH] Staging : android: binder.c: Prefer seq_puts to seq_printf Mathieu Rhéaume
2013-10-02 2:19 ` Joe Perches
2013-10-02 5:15 ` Ryan Mallon
2013-10-02 6:35 ` Joe Perches
2013-10-02 7:55 ` Dan Carpenter [this message]
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=20131002075539.GV6192@mwanda \
--to=dan.carpenter@oracle.com \
--cc=arve@android.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu@codingrhemes.com \
--cc=mirsal@mirsal.fr \
--cc=serban.constantinescu@arm.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