All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Rob Jones <rob.jones@codethink.co.uk>,
	Steven Whitehouse <swhiteho@redhat.com>,
	linux-fsdevel@vger.kernel.org
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-kernel@lists.codethink.co.uk, viro@ZenIV.linux.org.uk,
	ebiederm@xmission.com, ian.molton@codethink.co.uk
Subject: Re: [PATCH V3] seq_file: Document seq_open_private(), seq_release_private()
Date: Thu, 28 Aug 2014 16:29:00 -0700	[thread overview]
Message-ID: <53FFBB3C.8010207@infradead.org> (raw)
In-Reply-To: <53FC6872.3060800@codethink.co.uk>

On 08/26/14 03:58, Rob Jones wrote:
> Are there any other responses on this please? It seems pretty
> uncontentious. Maybe everyone was at LinuxCon last week.
> 
> On 18/08/14 12:50, Steven Whitehouse wrote:
>> Hi,
>>
>> On 18/08/14 12:40, Rob Jones wrote:
>>> Despite the fact that these functions have been around for years, they
>>> are
>>> little used (only 15 uses in 13 files at the preseht time) even though
>>> many other files use work-arounds to achieve the same result.
>>>
>>> By documenting them, hopefully they will become more widely used.
>>>
>>> Signed-off-by: Rob Jones <rob.jones@codethink.co.uk>
>> Acked-by: Steven Whitehouse <swhiteho@redhat.com>

Applied.  Thanks.

-- 
~Randy

      reply	other threads:[~2014-08-28 23:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-18 11:40 [PATCH V3] seq_file: Document seq_open_private(), seq_release_private() Rob Jones
2014-08-18 11:50 ` Steven Whitehouse
2014-08-26 10:58   ` Rob Jones
2014-08-28 23:29     ` Randy Dunlap [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=53FFBB3C.8010207@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=ebiederm@xmission.com \
    --cc=ian.molton@codethink.co.uk \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@lists.codethink.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob.jones@codethink.co.uk \
    --cc=swhiteho@redhat.com \
    --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 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.