From: Alexey Dobriyan <adobriyan@gmail.com>
To: Phillip Lougher <phillip@lougher.demon.co.uk>
Cc: akpm@linux-foundation.org, linux-embedded@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
tim.bird@am.sony.com
Subject: Re: [PATCH V2 14/16] Squashfs: Kconfig entry
Date: Wed, 29 Oct 2008 05:15:05 +0300 [thread overview]
Message-ID: <20081029021505.GA977@x200.localdomain> (raw)
In-Reply-To: <E1Kv0C4-0006Hm-Jz@dylan>
On Wed, Oct 29, 2008 at 01:49:56AM +0000, Phillip Lougher wrote:
> fs/Kconfig | 52 ++++++++++++++++++++++++++++++++++++++++++++++++++++
> --- a/fs/Kconfig
> +++ b/fs/Kconfig
> @@ -931,6 +931,58 @@ config CRAMFS
>
> If unsure, say N.
>
> +config SQUASHFS
No, no, no. Add fs/squashfs/Kconfig and source it from fs/Kconfig.
prev parent reply other threads:[~2008-10-29 2:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 1:49 [PATCH V2 14/16] Squashfs: Kconfig entry Phillip Lougher
2008-10-29 2:15 ` Alexey Dobriyan [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=20081029021505.GA977@x200.localdomain \
--to=adobriyan@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=phillip@lougher.demon.co.uk \
--cc=tim.bird@am.sony.com \
/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).