From: hooanon05@yahoo.co.jp
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [Aufs 02/25] aufs public header file
Date: Mon, 09 Mar 2009 17:30:09 +0900 [thread overview]
Message-ID: <9910.1236587409@jrobl> (raw)
In-Reply-To: <20090309055030.GB14122@uranus.ravnborg.org>
Sam Ravnborg:
> > include/linux/aufs_type.h | 98 +++++++++++++++++++++++++++++++++++++++++++++
>
> Why does it live in include/linux?
> If it is part of the userspace ABI it should be included in Kbuild.
It contains ioctl commands and other macros for userspace.
I will add this file in include/linux/Kbuild.
Thank you
J. R. Okajima
next prev parent reply other threads:[~2009-03-09 8:30 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-09 3:24 [Aufs 00/25] source files J. R. Okajima
2009-03-09 3:24 ` [Aufs 01/25] aufs documents J. R. Okajima
2009-03-09 5:48 ` Sam Ravnborg
2009-03-09 8:28 ` hooanon05
2009-03-09 3:24 ` [Aufs 02/25] aufs public header file J. R. Okajima
2009-03-09 5:50 ` Sam Ravnborg
2009-03-09 8:30 ` hooanon05 [this message]
2009-03-09 3:24 ` [Aufs 03/25] aufs module global J. R. Okajima
2009-03-09 5:51 ` Sam Ravnborg
2009-03-09 3:24 ` [Aufs 04/25] aufs super_block J. R. Okajima
2009-03-09 3:24 ` [Aufs 05/25] aufs branch directory/filesystem J. R. Okajima
2009-03-09 3:24 ` [Aufs 06/25] aufs xino J. R. Okajima
2009-03-09 3:25 ` [Aufs 07/25] aufs object lifetime management via sysfs J. R. Okajima
2009-03-09 3:25 ` [Aufs 08/25] aufs mount options/flags J. R. Okajima
2009-03-09 3:25 ` [Aufs 09/25] aufs workqueue J. R. Okajima
2009-03-09 3:25 ` [Aufs 10/25] aufs sub-VFS J. R. Okajima
2009-03-09 3:25 ` [Aufs 11/25] aufs sub-dcache J. R. Okajima
2009-03-09 3:25 ` [Aufs 12/25] aufs copy-up J. R. Okajima
2009-03-09 3:25 ` [Aufs 13/25] aufs whiteout J. R. Okajima
2009-03-09 3:25 ` [Aufs 14/25] aufs pseudo-link J. R. Okajima
2009-03-09 3:25 ` [Aufs 15/25] aufs policies to select one among multiple writable branches J. R. Okajima
2009-03-09 3:25 ` [Aufs 16/25] aufs dentry and lookup J. R. Okajima
2009-03-09 3:25 ` [Aufs 17/25] aufs file J. R. Okajima
2009-03-09 3:25 ` [Aufs 18/25] aufs direcotry J. R. Okajima
2009-03-09 3:25 ` [Aufs 19/25] aufs inode J. R. Okajima
2009-03-09 3:25 ` [Aufs 20/25] aufs ioctl J. R. Okajima
2009-03-09 3:25 ` [Aufs 21/25] aufs sysfs entries J. R. Okajima
2009-03-09 3:25 ` [Aufs 22/25] aufs branch for loopback block device J. R. Okajima
2009-03-09 3:25 ` [Aufs 23/25] aufs internal inotify J. R. Okajima
2009-03-09 3:25 ` [Aufs 24/25] aufs test for fstype J. R. Okajima
2009-03-09 3:25 ` [Aufs 25/25] aufs debug J. R. Okajima
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=9910.1236587409@jrobl \
--to=hooanon05@yahoo.co.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
/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