From: Marco Stornelli <marco.stornelli@gmail.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Linux Embedded <linux-embedded@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] Kconfig: XIP doesn't depend on block
Date: Mon, 7 Feb 2011 08:52:41 +0100 [thread overview]
Message-ID: <AANLkTi=T3TGYcxm2=C6QtYss09H9R+m0Zk9KDQepMqiL@mail.gmail.com> (raw)
In-Reply-To: <20110206084440.a6c2df3b.rdunlap@xenotime.net>
2011/2/6 Randy Dunlap <rdunlap@xenotime.net>:
> On Sun, 06 Feb 2011 16:15:00 +0100 Marco Stornelli wrote:
>
>> From: Marco Stornelli <marco.stornelli@gmail.com>
>>
>> XIP doesn't depend on block symbol, then we can reorder the Kconfig.
>> For ext2 doesn't change the Kconfig behavior but if other fs will use
>> FS_XIP it won't need to include block support if not needed.
>
> Hi Marco,
>
> Do you know of a filesystem where this matters?
>
Yes, for example mine (pramfs) :)
>> Signed-off-by: Marco Stornelli <marco.stornelli@gmail.com>
>> ---
>>
>> --- Kconfig.orig 2011-01-19 00:14:02.000000000 +0100
>> +++ Kconfig 2011-02-06 16:04:51.000000000 +0100
>
> This filename should include path, like
> --- fs/Kconfig.orig
> +++ fs/Kconfig
>
>> @@ -9,13 +9,6 @@ if BLOCK
>> source "fs/ext2/Kconfig"
>> source "fs/ext3/Kconfig"
>> source "fs/ext4/Kconfig"
>> -
>
> The 3 filesystems above are immediately under:
>
> if BLOCK
>
> so ext[234] depend on BLOCK. Why would it matter about FS_XIP?
>
I don't know but for example even POSIX ACL was under "if BLOCK",
maybe there is only an historical refuse.
Marco
prev parent reply other threads:[~2011-02-07 7:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-06 15:15 [PATCH] Kconfig: XIP doesn't depend on block Marco Stornelli
2011-02-06 16:44 ` Randy Dunlap
2011-02-07 7:52 ` Marco Stornelli [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='AANLkTi=T3TGYcxm2=C6QtYss09H9R+m0Zk9KDQepMqiL@mail.gmail.com' \
--to=marco.stornelli@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.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 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).