mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rob Jones <rob.jones@codethink.co.uk>
To: linux-kernel@vger.kernel.org
Cc: ocfs2-devel@oss.oracle.com, dan.carpenter@oracle.com,
	akpm@linux-foundation.org, jlbec@evilplan.org, mfasheh@suse.com,
	linux-kernel@codethink.co.uk, rob.jones@codethink.co.uk
Subject: [PATCH 0/3] fs: ocfs2: use seq_open_private()
Date: Wed, 10 Sep 2014 15:49:15 +0100	[thread overview]
Message-ID: <1410360558-28399-1-git-send-email-rob.jones@codethink.co.uk> (raw)

Use seq_open_private() and __seq_open_private() to reduce boilerplate
code in ocfs2.

These two functions have been around, undocumented, for years. They can
simplify the set up code for seq file operations.

Note that sparse complains about all three files in this series but the
problems are outside the remit of this patch series.

Signed-off-by: Rob Jones <rob.jones@codethink.co.uk>

Rob Jones (3):
  fs: ocfs2: use seq_open_private() not seq_open()
  fs: ocfs2: use seq_open_private() not seq_open()
  fs: ocfs2: Use __seq_open_private() not seq_open()

 fs/ocfs2/cluster/netdebug.c |   78 +++++++++++--------------------------------
 fs/ocfs2/dlm/dlmdebug.c     |   39 ++++++++--------------
 fs/ocfs2/dlmglue.c          |   23 +++----------
 3 files changed, 38 insertions(+), 102 deletions(-)

-- 
1.7.10.4


             reply	other threads:[~2014-09-10 14:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-10 14:49 Rob Jones [this message]
2014-09-10 14:49 ` [PATCH 1/3] fs: ocfs2: use seq_open_private() not seq_open() Rob Jones
2014-09-10 14:49 ` [PATCH 2/3] " Rob Jones
2014-09-10 14:49 ` [PATCH 3/3] fs: ocfs2: Use __seq_open_private() " Rob Jones

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=1410360558-28399-1-git-send-email-rob.jones@codethink.co.uk \
    --to=rob.jones@codethink.co.uk \
    --cc=akpm@linux-foundation.org \
    --cc=dan.carpenter@oracle.com \
    --cc=jlbec@evilplan.org \
    --cc=linux-kernel@codethink.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfasheh@suse.com \
    --cc=ocfs2-devel@oss.oracle.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

all inboxes | Powered by JetHome®