From: Joe Perches <joe@perches.com>
To: Alexander Viro <viro@zeniv.linux.org.uk>
Cc: linux-kernel@vger.kernel.org, cluster-devel@redhat.com,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH -next 0/4] fs: Use seq_is_buf_full
Date: Wed, 08 Jan 2014 09:47:42 -0800 [thread overview]
Message-ID: <1389203262.24222.3.camel@joe-AO722> (raw)
In-Reply-To: <cover.1386891757.git.joe@perches.com>
On Thu, 2013-12-12 at 15:47 -0800, Joe Perches wrote:
> Convert the fs uses and misuses of seq_printf to void
>
> These patches depend on https://lkml.org/lkml/2013/12/11/714
>
> Joe Perches (4):
> dlm: Use seq_is_buf_full - remove seq_printf returns
> dlm: Use seq_puts, remove unnecessary trailing spaces
> fs: Convert show_fdinfo functions to void
> debugfs: Fix misuse of seq_printf return value
Ping?
> fs/debugfs/file.c | 14 +--
> fs/dlm/debug_fs.c | 274 +++++++++++++++++++++++++----------------------------
> fs/eventfd.c | 15 +--
> fs/eventpoll.c | 19 ++--
> fs/notify/fdinfo.c | 68 ++++++-------
> fs/notify/fdinfo.h | 4 +-
> fs/proc/fd.c | 2 +-
> fs/signalfd.c | 10 +-
> include/linux/fs.h | 2 +-
> 9 files changed, 184 insertions(+), 224 deletions(-)
>
prev parent reply other threads:[~2014-01-08 17:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 3:44 [PATCH -next 0/2] seq_file/netfilter: Start removing returns from seq_<foo> Joe Perches
2013-12-12 3:44 ` [PATCH -next 1/2] seq_file: Rename static bool seq_overflow to public bool seq_is_buf_full Joe Perches
2013-12-12 23:47 ` [PATCH -next 0/4] fs: Use seq_is_buf_full Joe Perches
2013-12-12 23:47 ` [PATCH -next 3/4] fs: Convert show_fdinfo functions to void Joe Perches
2014-01-08 17:47 ` Joe Perches [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=1389203262.24222.3.camel@joe-AO722 \
--to=joe@perches.com \
--cc=cluster-devel@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).