From: Theodore Tso <tytso@MIT.EDU>
To: Christoph Hellwig <hch@lst.de>
Cc: akpm@osdl.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] don't export ext3_fs.h and jbd.h
Date: Wed, 26 Mar 2008 19:30:38 -0400 [thread overview]
Message-ID: <20080326233038.GE7202@mit.edu> (raw)
In-Reply-To: <20080326224622.GA12273@lst.de>
On Wed, Mar 26, 2008 at 11:46:22PM +0100, Christoph Hellwig wrote:
> either of the headers actually compiles when included from userpsace
> nor should it be made available as userspace tools should be using
> the libraries or at least headers from e2fsprogs.
I was planning on simply moving ext3_fs.h to fs/ext3, per your
previously submitted patches.
I agree that removing jbd.h from the exported list makes sense.
Acked-by: "Theodore Ts'o" <tytso@mit.edu>
- Ted
next prev parent reply other threads:[~2008-03-26 23:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 22:46 [PATCH] don't export ext3_fs.h and jbd.h Christoph Hellwig
2008-03-26 23:30 ` Theodore Tso [this message]
2008-03-26 23:37 ` Christoph Hellwig
2008-03-27 10:01 ` Theodore Tso
2008-03-27 10:14 ` Andrew Morton
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=20080326233038.GE7202@mit.edu \
--to=tytso@mit.edu \
--cc=akpm@osdl.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).