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, 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 01:19:13 +0100 [thread overview]
Message-ID: <20070809001913.GA10044@infradead.org> (raw)
In-Reply-To: <20070808162447.GT15319@lazybastard.org>
On Wed, Aug 08, 2007 at 06:24:47PM +0200, J??rn Engel wrote:
> --- linux-2.6.21logfs/include/linux/Kbuild~logfs 2007-08-08 02:57:37.000000000 +0200
> +++ linux-2.6.21logfs/include/linux/Kbuild 2007-08-08 02:57:37.000000000 +0200
> @@ -101,6 +101,7 @@ header-y += jffs2.h
> header-y += keyctl.h
> header-y += limits.h
> header-y += lock_dlm_plock.h
> +header-y += logfs.h
That file doesn't define any kind of user<->kernel interface and thus should
not be exported.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: J??rn Engel <joern@logfs.org>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mtd@lists.infradead.org, akpm@osdl.org,
David Woodhouse <dwmw2@infradead.org>,
Arnd Bergmann <arnd@arndb.de>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [Patch 18/18] include/linux/Kbuild
Date: Thu, 9 Aug 2007 01:19:13 +0100 [thread overview]
Message-ID: <20070809001913.GA10044@infradead.org> (raw)
In-Reply-To: <20070808162447.GT15319@lazybastard.org>
On Wed, Aug 08, 2007 at 06:24:47PM +0200, J??rn Engel wrote:
> --- linux-2.6.21logfs/include/linux/Kbuild~logfs 2007-08-08 02:57:37.000000000 +0200
> +++ linux-2.6.21logfs/include/linux/Kbuild 2007-08-08 02:57:37.000000000 +0200
> @@ -101,6 +101,7 @@ header-y += jffs2.h
> header-y += keyctl.h
> header-y += limits.h
> header-y += lock_dlm_plock.h
> +header-y += logfs.h
That file doesn't define any kind of user<->kernel interface and thus should
not be exported.
next prev parent reply other threads:[~2007-08-09 0:19 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 16:12 LogFS take five Jörn Engel
2007-08-08 16:12 ` Jörn Engel
2007-08-08 16:13 ` [Patch 01/18] fs/logfs/Makefile Jörn Engel
2007-08-08 16:13 ` Jörn Engel
2007-08-08 16:14 ` [Patch 02/18] include/linux/logfs.h Jörn Engel
2007-08-08 16:14 ` Jörn Engel
2007-08-08 22:56 ` Arnd Bergmann
2007-08-08 22:56 ` Arnd Bergmann
2007-08-08 22:56 ` Arnd Bergmann
2007-08-09 20:03 ` Jörn Engel
2007-08-09 20:03 ` Jörn Engel
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 ` Jörn Engel
2007-08-08 16:15 ` [Patch 04/18] fs/logfs/compr.c Jörn Engel
2007-08-08 16:15 ` Jörn Engel
2007-08-08 16:16 ` [Patch 05/18] fs/logfs/dir.c Jörn Engel
2007-08-08 16:16 ` Jörn Engel
2007-08-08 17:07 ` Artem Bityutskiy
2007-08-08 17:07 ` Artem Bityutskiy
2007-08-08 17:15 ` Jörn Engel
2007-08-08 17:15 ` Jörn Engel
2007-08-08 17:15 ` Jörn Engel
2007-08-08 17:34 ` Artem Bityutskiy
2007-08-08 17:34 ` Artem Bityutskiy
2007-08-08 17:41 ` Jörn Engel
2007-08-08 17:41 ` Jörn Engel
2007-08-08 17:41 ` Jörn Engel
2007-08-08 18:50 ` Artem Bityutskiy
2007-08-08 18:50 ` Artem Bityutskiy
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 ` Jörn Engel
2007-08-08 16:17 ` [Patch 07/18] fs/logfs/gc.c Jörn Engel
2007-08-08 16:17 ` Jörn Engel
2007-08-08 16:18 ` [Patch 08/18] fs/logfs/inode.c Jörn Engel
2007-08-08 16:18 ` Jörn Engel
2007-08-08 16:19 ` [Patch 08/18] fs/logfs/journal.c Jörn Engel
2007-08-08 16:19 ` Jörn Engel
2007-08-08 16:19 ` [Patch 10/18] fs/logfs/memtree.c Jörn Engel
2007-08-08 16:19 ` Jörn Engel
2007-08-08 16:20 ` [Patch 11/18] fs/logfs/readwrite.c Jörn Engel
2007-08-08 16:20 ` Jörn Engel
2007-08-08 16:20 ` [Patch 12/18] fs/logfs/segment.c Jörn Engel
2007-08-08 16:20 ` Jörn Engel
2007-08-08 16:21 ` [Patch 13/18] fs/logfs/super.c Jörn Engel
2007-08-08 16:21 ` Jörn Engel
2007-08-08 16:22 ` [Patch 14/18] fs/logfs/progs/fsck.c Jörn Engel
2007-08-08 16:22 ` Jörn Engel
2007-08-08 16:22 ` [Patch 15/18] fs/logfs/Locking Jörn Engel
2007-08-08 16:22 ` Jörn Engel
2007-08-08 16:23 ` [Patch 16/18] fs/Kconfig Jörn Engel
2007-08-08 16:23 ` Jörn Engel
2007-08-08 23:01 ` Arnd Bergmann
2007-08-08 23:01 ` Arnd Bergmann
2007-08-08 23:01 ` Arnd Bergmann
2007-08-09 20:03 ` Jörn Engel
2007-08-09 20:03 ` Jörn Engel
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 ` Jörn Engel
2007-08-08 16:24 ` [Patch 18/18] include/linux/Kbuild Jörn Engel
2007-08-08 16:24 ` Jörn Engel
2007-08-09 0:19 ` Christoph Hellwig [this message]
2007-08-09 0:19 ` Christoph Hellwig
2007-08-09 2:32 ` Jörn Engel
2007-08-09 2:32 ` Jörn Engel
2007-08-09 2:39 ` Christoph Hellwig
2007-08-09 2:39 ` Christoph Hellwig
2007-08-09 2:39 ` Jörn Engel
2007-08-09 2:39 ` Jörn Engel
2007-08-09 2:45 ` Christoph Hellwig
2007-08-09 2:45 ` Christoph Hellwig
2007-08-08 16:27 ` LogFS take five Artem Bityutskiy
2007-08-08 16:27 ` Artem Bityutskiy
2007-08-08 16:35 ` Jörn Engel
2007-08-08 16:35 ` Jörn Engel
2007-08-08 16:35 ` Jörn Engel
2007-08-08 16:52 ` Artem Bityutskiy
2007-08-08 16:52 ` Artem Bityutskiy
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=20070809001913.GA10044@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 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.