public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: [PATCH] xfs_io: add support for O_TMPFILE opens
Date: Thu, 20 Feb 2014 14:40:26 -0800	[thread overview]
Message-ID: <20140220224026.GA25054@infradead.org> (raw)
In-Reply-To: <20140220221518.GR4916@dastard>

On Fri, Feb 21, 2014 at 09:15:18AM +1100, Dave Chinner wrote:
> Can you also push this into the main CLI interface similar to how
> all the other open flags can be specified?

Sure.

> FWIW, any plans to add a "link" command to be able to link the
> tmpfile into the namespace once it is created?

I was planning to do that, but as pointed out in my next mail it seems
we don't actually have any other namespace commands in xfs_io, so I'm
starting to wonder if it's the right place.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2014-02-20 22:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-20 22:00 [PATCH] xfs_io: add support for O_TMPFILE opens Christoph Hellwig
2014-02-20 22:15 ` Dave Chinner
2014-02-20 22:40   ` Christoph Hellwig [this message]
2014-02-21  0:16 ` Shaun Gosse
2014-02-21  0:20   ` Christoph Hellwig
2014-02-21  0:30 ` [PATCH v2] " Christoph Hellwig
2014-02-23 21:01   ` Dave Chinner
2014-02-21  0:49 ` [PATCH] xfs_io: add support for flink Christoph Hellwig
2014-02-23 21:06   ` Dave Chinner
2014-02-25 19:52   ` [PATCH v2] " Christoph Hellwig
2014-02-25 23:35     ` Dave Chinner
2014-03-13 10:09       ` Christoph Hellwig
2014-03-13 10:21         ` Dave Chinner
2014-03-13 10:42           ` Dave Chinner

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=20140220224026.GA25054@infradead.org \
    --to=hch@infradead.org \
    --cc=david@fromorbit.com \
    --cc=xfs@oss.sgi.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