From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Brian Norris <computersforpeace@gmail.com>
Cc: Linux mtd <linux-mtd@lists.infradead.org>,
David Woodhouse <dwmw2@infradead.org>,
Ricard Wanderlof <ricard.wanderlof@axis.com>,
Kees Cook <keescook@chromium.org>
Subject: Re: JFFS2 SUMMARY prior to Linux 3.9
Date: Wed, 2 Oct 2013 11:22:27 -0700 [thread overview]
Message-ID: <20131002182227.GA7065@kroah.com> (raw)
In-Reply-To: <CAN8TOE8PLvcK4kuRvbRh32gg0_Y8sbwWjdcWh_xt-tgQcPb85Q@mail.gmail.com>
On Wed, Oct 02, 2013 at 10:57:04AM -0700, Brian Norris wrote:
> On Mon, Sep 16, 2013 at 1:04 AM, Ricard Wanderlof
> <ricard.wanderlof@axis.com> wrote:
> > I've noticed that JFFS2 summary has been relieved of it's EXPERIMENTAL
> > status since Linux 3.9 . But was it stable enough before then as well? -
> > often the EXPERIMENTAL property lingers on longer that it really needs to.
>
> AFAIK, JFFS2 hasn't changed much for many releases, so its current
> status pretty well reflects its status for many previous releases.
>
> Regarding the EXPERIMENTAL status; this was changed without CC'ing the
> MTD list (although David was CC'd, it seems) in commit:
>
> commit cf98c5e56807af7c793497bbd0446f71c383ffd5
> Author: Kees Cook <keescook@chromium.org>
> Date: Wed Jan 16 18:54:12 2013 -0800
>
> fs/jffs2: remove depends on CONFIG_EXPERIMENTAL
>
> Judging by the commit description, this change just represents a
> change in attitude toward the CONFIG_EXPERIMENTAL Kconfig option
> rather than any particular judgment of JFFS2 summary support.
CONFIG_EXPERIMENTAL was removed from the entire kernel, as it really
didn't mean anything anymore, and hadn't for _years_.
greg k-h
next prev parent reply other threads:[~2013-10-02 18:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 8:04 JFFS2 SUMMARY prior to Linux 3.9 Ricard Wanderlof
2013-10-02 17:57 ` Brian Norris
2013-10-02 18:22 ` Greg Kroah-Hartman [this message]
2013-10-02 18:31 ` Kees Cook
2013-10-03 6:57 ` Ricard Wanderlof
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=20131002182227.GA7065@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=keescook@chromium.org \
--cc=linux-mtd@lists.infradead.org \
--cc=ricard.wanderlof@axis.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 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.