From: Christoph Hellwig <hch@infradead.org>
To: J??rn Engel <joern@logfs.org>
Cc: akpm@osdl.org, Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
linux-mtd@lists.infradead.org, linux-fsdevel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [Patch 18/18] include/linux/Kbuild
Date: Thu, 9 Aug 2007 03:45:24 +0100 [thread overview]
Message-ID: <20070809024524.GB18792@infradead.org> (raw)
In-Reply-To: <20070809023920.GB3321@lazybastard.org>
On Thu, Aug 09, 2007 at 04:39:20AM +0200, J??rn Engel wrote:
> Fair enough. Does the file still make sense in include/linux/ then?
I don't think so. Except for the one filesystem that's out there to repeat
past mistakes all recent ones keep their headers in their impleementation
directories.
next prev parent reply other threads:[~2007-08-09 2:45 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 16:12 LogFS take five Jörn Engel
2007-08-08 16:13 ` [Patch 01/18] fs/logfs/Makefile Jörn Engel
2007-08-08 16:14 ` [Patch 02/18] include/linux/logfs.h Jörn Engel
2007-08-08 22:56 ` Arnd Bergmann
2007-08-09 20:03 ` Jörn Engel
2007-08-08 16:15 ` [Patch 03/18] fs/logfs/logfs.h Jörn Engel
2007-08-08 16:15 ` [Patch 04/18] fs/logfs/compr.c Jörn Engel
2007-08-08 16:16 ` [Patch 05/18] fs/logfs/dir.c Jörn Engel
2007-08-08 17:07 ` Artem Bityutskiy
2007-08-08 17:15 ` Jörn Engel
2007-08-08 17:34 ` Artem Bityutskiy
2007-08-08 17:41 ` Jörn Engel
2007-08-08 18:50 ` Artem Bityutskiy
2007-08-08 16:17 ` [Patch 05/18] fs/logfs/file.c Jörn Engel
2007-08-08 16:17 ` [Patch 07/18] fs/logfs/gc.c Jörn Engel
2007-08-08 16:18 ` [Patch 08/18] fs/logfs/inode.c Jörn Engel
2007-08-08 16:19 ` [Patch 08/18] fs/logfs/journal.c Jörn Engel
2007-08-08 16:19 ` [Patch 10/18] fs/logfs/memtree.c Jörn Engel
2007-08-08 16:20 ` [Patch 11/18] fs/logfs/readwrite.c Jörn Engel
2007-08-08 16:20 ` [Patch 12/18] fs/logfs/segment.c Jörn Engel
2007-08-08 16:21 ` [Patch 13/18] fs/logfs/super.c Jörn Engel
2007-08-08 16:22 ` [Patch 14/18] fs/logfs/progs/fsck.c Jörn Engel
2007-08-08 16:22 ` [Patch 15/18] fs/logfs/Locking Jörn Engel
2007-08-08 16:23 ` [Patch 16/18] fs/Kconfig Jörn Engel
2007-08-08 23:01 ` Arnd Bergmann
2007-08-09 20:03 ` Jörn Engel
2007-08-08 16:24 ` [Patch 17/18] fs/Makefile Jörn Engel
2007-08-08 16:24 ` [Patch 18/18] include/linux/Kbuild Jörn Engel
2007-08-09 0:19 ` Christoph Hellwig
2007-08-09 2:32 ` Jörn Engel
2007-08-09 2:39 ` Christoph Hellwig
2007-08-09 2:39 ` Jörn Engel
2007-08-09 2:45 ` Christoph Hellwig [this message]
2007-08-08 16:27 ` LogFS take five Artem Bityutskiy
2007-08-08 16:35 ` Jörn Engel
2007-08-08 16:52 ` Artem Bityutskiy
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=20070809024524.GB18792@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=arnd@arndb.de \
--cc=dwmw2@infradead.org \
--cc=joern@logfs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=tglx@linutronix.de \
/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