LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: Grzegorz Kulewski <kangur@polcom.net>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
akpm@osdl.org
Subject: Re: [PATCH] linux/magic.h for magic numbers
Date: Sat, 9 Sep 2006 15:33:34 +0200 [thread overview]
Message-ID: <20060909133334.GB17085@uranus.ravnborg.org> (raw)
In-Reply-To: <4502C086.2080302@garzik.org>
On Sat, Sep 09, 2006 at 09:24:22AM -0400, Jeff Garzik wrote:
> Grzegorz Kulewski 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.
> >
> >But... if some patch changes this file (like adding new magic symbol) it
> >will cause large part of the kernel to rebuild without any good reason. No?
>
> No :)
>
> * The days when linux/fs.h included individual filesystem headers is
> long gone. Only the filesystems themselves typically include the
> linux/foo_fs*.h files these days.
But do we want one common set of magic numbers or do we try to divide it
up per subssystem. The lattter approach are used for many other purposes
so why not for magics too?
Or in other word magic.h => fs_magic.h
Sam
next prev parent reply other threads:[~2006-09-09 13:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-09 11:02 Jeff Garzik
2006-09-09 12:58 ` Grzegorz Kulewski
2006-09-09 13:24 ` Jeff Garzik
2006-09-09 13:33 ` Sam Ravnborg [this message]
2006-09-09 13:44 ` Jeff Garzik
2006-09-12 8:22 ` Ian Kent
2006-09-12 9:33 ` Jan Engelhardt
2006-09-12 12:30 ` Jeff Garzik
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=20060909133334.GB17085@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@osdl.org \
--cc=jeff@garzik.org \
--cc=kangur@polcom.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: [PATCH] linux/magic.h for magic numbers' \
/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
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).