From: David Miller <davem@davemloft.net>
To: hch@infradead.org
Cc: bunk@kernel.org, vapier@gentoo.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [patch] linux/ufs_fs.h: use __u64 for userspace
Date: Wed, 02 Jan 2008 00:04:44 -0800 (PST) [thread overview]
Message-ID: <20080102.000444.18510965.davem@davemloft.net> (raw)
In-Reply-To: <20080102075033.GA16267@infradead.org>
From: Christoph Hellwig <hch@infradead.org>
Date: Wed, 2 Jan 2008 07:50:33 +0000
> The only non-kernel user of this known to me is silo, which should just
> have it's own header documenting the solaris sparc ufs variant it needs
> to understand, possibly by using a copy of the kernel version at any
> given point of time.
And this is what the current SILO sources do.
next prev parent reply other threads:[~2008-01-02 8:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-02 1:51 [patch] linux/ufs_fs.h: use __u64 for userspace Mike Frysinger
2008-01-02 2:02 ` Adrian Bunk
2008-01-02 7:50 ` Christoph Hellwig
2008-01-02 8:04 ` David Miller [this message]
2008-01-02 8:10 ` Christoph Hellwig
2008-01-02 13:40 ` [patch] linux/ufs_fs.h: do not export to userspace anymore Mike Frysinger
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=20080102.000444.18510965.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.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 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.