From: Mark Brown <broonie@kernel.org>
To: Joe Perches <joe@perches.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
"James E.J. Bottomley" <jejb@parisc-linux.org>,
Helge Deller <deller@gmx.de>, Liam Girdwood <lgirdwood@gmail.com>,
Wim Van Sebroeck <wim@iguana.be>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Petr Mladek <pmladek@suse.cz>, Felipe Balbi <balbi@ti.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-parisc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, linux-watchdog@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH -next 1/2] seq_puts: Convert to return void and convert uses too.
Date: Tue, 11 Nov 2014 00:32:36 +0000 [thread overview]
Message-ID: <20141111003236.GS3815@sirena.org.uk> (raw)
In-Reply-To: <c8249a5c6504275a0e22704dda83b34002a89eac.1415645476.git.joe@perches.com>
[-- Attachment #1: Type: text/plain, Size: 191 bytes --]
On Mon, Nov 10, 2014 at 10:58:56AM -0800, Joe Perches wrote:
> Using the return value of seq_puts is error-prone, so
> make it return void instead.
Acked-by: Mark Brown <broonie@kernel.org>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-11-11 0:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 18:58 [PATCH -next 0/2] seq: Convert seq_puts and seq_putc to return void Joe Perches
[not found] ` <cover.1415645476.git.joe-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
2014-11-10 18:58 ` [PATCH -next 1/2] seq_puts: Convert to return void and convert uses too Joe Perches
2014-11-10 18:58 ` Joe Perches
2014-11-11 0:32 ` Mark Brown [this message]
2014-11-11 13:38 ` Petr Mladek
2014-11-10 18:58 ` [PATCH -next 2/2] seq_putc: " Joe Perches
2014-11-10 18:58 ` Joe Perches
2014-11-11 13:47 ` Petr Mladek
2014-11-12 12:29 ` Pablo Neira Ayuso
2014-11-12 15:25 ` Corey Minyard
2014-11-12 15:25 ` Corey Minyard
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=20141111003236.GS3815@sirena.org.uk \
--to=broonie@kernel.org \
--cc=balbi@ti.com \
--cc=deller@gmx.de \
--cc=gregkh@linuxfoundation.org \
--cc=jejb@parisc-linux.org \
--cc=joe@perches.com \
--cc=lgirdwood@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=pmladek@suse.cz \
--cc=rostedt@goodmis.org \
--cc=viro@zeniv.linux.org.uk \
--cc=wim@iguana.be \
/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.