From: Jeff Garzik <jeff@garzik.org>
To: Ian Kent <raven@themaw.net>, akpm@osdl.org
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] linux/magic.h for magic numbers
Date: Tue, 12 Sep 2006 08:30:38 -0400 [thread overview]
Message-ID: <4506A86E.7000105@garzik.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0609121620550.4911@raven.themaw.net>
Ian Kent wrote:
> On Sat, 9 Sep 2006, Jeff Garzik wrote:
>
>> An IRC discussion sparked a memory: most filesystems really don't
>> need to put anything at all in include/linux. Excluding API-ish
>> filesystems like procfs, just about the only filesystem symbols that
>> get exported outside of __KERNEL__ are the *_SUPER_MAGIC symbols,
>> and similar symbols.
>>
>> After seeing the useful attributes of linux/poison.h, I propose a
>> similar linux/magic.h.
>>
>> We can see from the patch below that this permitted the deletion of a
>> couple headers, where the *_SUPER_MAGIC symbol was the only thing in the
>> entire header.
>>
>> Other non-filesystem-related magic numbers could get moved here
>> eventually, if maintainers so desire, but I wanted to start off with the
>> obvious low-hanging fruit.
>>
>
> Would be good to include autofs in this lot.
>
> Defined in linux/autofs/autofs_i.h
> Defined in linux/autofs4/autofs_i.h
>
> as
>
> #define AUTOFS_SUPER_MAGIC 0x0187
Updated.
Andrew, please add the "magic" branch of
git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/misc-2.6.git
to the list of trees you pull.
Thanks,
Jeff
prev parent reply other threads:[~2006-09-12 12:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-09 11:02 [PATCH] linux/magic.h for magic numbers Jeff Garzik
2006-09-09 12:58 ` Grzegorz Kulewski
2006-09-09 13:24 ` Jeff Garzik
2006-09-09 13:33 ` Sam Ravnborg
2006-09-09 13:44 ` Jeff Garzik
2006-09-11 2:59 ` 64bit JBD patch 张军伟
2006-09-12 8:22 ` [PATCH] linux/magic.h for magic numbers Ian Kent
2006-09-12 9:33 ` Jan Engelhardt
2006-09-12 12:30 ` Jeff Garzik [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=4506A86E.7000105@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@osdl.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
/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.