All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 2/2] Ocfs2: Implement new OCFS2_IOC_INFO ioctl for ocfs2.
Date: Mon, 30 Nov 2009 01:36:42 -0800	[thread overview]
Message-ID: <20091130093641.GA5456@mail.oracle.com> (raw)
In-Reply-To: <87tywf4szb.fsf@basil.nowhere.org>

On Fri, Nov 27, 2009 at 09:23:36PM +0100, Andi Kleen wrote:
> It's unclear why you just can't use separate ioctls for each request.

	Because we're going to be adding many info requests, with more
over time.  Much nicer to pass in a list of requests than have a hundred
or more ioctls.  Plus we can do fun versioning.

Joel

-- 

"Sometimes I think the surest sign intelligent
 life exists elsewhere in the universe is that
 none of it has tried to contact us."
                                -Calvin & Hobbes

Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127

  parent reply	other threads:[~2009-11-30  9:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-27  8:24 [Ocfs2-devel] [PATCH 1/2] Ocfs2: Add new ioctls prototype and corresponding data structure to ocfs2 header Tristan Ye
2009-11-27  8:24 ` [Ocfs2-devel] [PATCH 2/2] Ocfs2: Implement new OCFS2_IOC_INFO ioctl for ocfs2 Tristan Ye
2009-11-27 20:23   ` Andi Kleen
2009-11-28  2:49     ` Tristan
2009-11-30  9:36     ` Joel Becker [this message]
2009-11-30 23:49   ` Sunil Mushran
2009-12-01  1:25     ` Tristan
2009-12-02  0:16       ` Sunil Mushran
2009-12-01  3:20     ` Tristan
2009-12-02  0:35       ` Joel Becker
2009-12-02  2:29         ` Tristan
2009-12-02 18:28           ` Joel Becker
2009-11-30 22:57 ` [Ocfs2-devel] [PATCH 1/2] Ocfs2: Add new ioctls prototype and corresponding data structure to ocfs2 header Sunil Mushran
2009-12-01  1:15   ` Tristan

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=20091130093641.GA5456@mail.oracle.com \
    --to=joel.becker@oracle.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 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.