From: Christoph Hellwig <hch@infradead.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: Christoph Hellwig <hch@infradead.org>,
dushistov@mail.ru, linux-kernel@vger.kernel.org,
sparc@gentoo.org
Subject: Re: [patch] export ufs_fs.h to userspace
Date: Thu, 8 Feb 2007 20:21:17 +0000 [thread overview]
Message-ID: <20070208202117.GA8429@infradead.org> (raw)
In-Reply-To: <200702081505.36513.vapier@gentoo.org>
On Thu, Feb 08, 2007 at 03:05:35PM -0500, Mike Frysinger wrote:
> > We should only export kernel interfaces and ufs_fs.h isn't one. silo
> > wants it because it defines the ufs format - but the linux structs for
> > that can and do change, e.g. adding unions when we add support for the
> > gazillion+1st ufs format variant. silo should just grab a copy of it
> > that it's happy with it and update it when it needs to support another
> > format variant (which I think is a rather theoretical issue as silo
> > only supports the solaris/sparc format IIR)
>
> seems logical to mean, thanks for the response
Btw, if you're interesting in helping out in this area a little bit,
it would be nice if we could split up and move ufs_fs.h a little bit.
We should have an:
fs/ufs/ufs.h for all driver internal declarations
fs/ufs/ufs_layout.h that purely defines the layout can can be copied
directly into other tools that need the ufs layout
like silo
prev parent reply other threads:[~2007-02-08 20:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 7:46 [patch] export ufs_fs.h to userspace Mike Frysinger
2007-02-08 10:33 ` Arjan van de Ven
2007-02-08 11:33 ` Alexey Dobriyan
2007-02-08 15:10 ` Mike Frysinger
2007-02-08 15:59 ` Arjan van de Ven
2007-02-08 16:12 ` Mike Frysinger
2007-02-08 20:02 ` Christoph Hellwig
2007-02-08 20:05 ` Mike Frysinger
2007-02-08 20:21 ` Christoph Hellwig [this message]
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=20070208202117.GA8429@infradead.org \
--to=hch@infradead.org \
--cc=dushistov@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=sparc@gentoo.org \
--cc=vapier@gentoo.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