linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Kees Cook <keescook@chromium.org>
Cc: Dan Williams <djbw@fb.com>, LKML <linux-kernel@vger.kernel.org>,
	linux-raid@vger.kernel.org,
	Arjan van de Ven <arjan@linux.intel.com>,
	Dan Williams <dan.j.williams@intel.com>,
	Alasdair G Kergon <agk@redhat.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] md/raid456: remove depends on CONFIG_EXPERIMENTAL
Date: Tue, 5 Mar 2013 08:11:02 +1100	[thread overview]
Message-ID: <20130305081102.73211ef9@notabene.brown> (raw)
In-Reply-To: <CAGXu5jKpdVFoEvbGv3K620XDx2bjqQYeCLE511h-071XaPQUGg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1740 bytes --]

On Mon, 4 Mar 2013 10:59:30 -0800 Kees Cook <keescook@chromium.org> wrote:

> On Tue, Feb 26, 2013 at 5:27 PM, Dan Williams <djbw@fb.com> wrote:
> > On Fri, Feb 22, 2013 at 11:40 PM, Kees Cook <keescook@chromium.org> wrote:
> >> The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
> >> while now and is almost always enabled by default. As agreed during the
> >> Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
> >>
> >> Signed-off-by: Kees Cook <keescook@chromium.org>
> >> Cc: Arjan van de Ven <arjan@linux.intel.com>
> >> Cc: Dan Williams <dan.j.williams@intel.com>
> >> Cc: Alasdair G Kergon <agk@redhat.com>
> >> ---
> >>  drivers/md/Kconfig |    1 -
> >>  1 file changed, 1 deletion(-)
> >>
> >> diff --git a/drivers/md/Kconfig b/drivers/md/Kconfig
> >> index 7cdf359..0cc3a3d 100644
> >> --- a/drivers/md/Kconfig
> >> +++ b/drivers/md/Kconfig
> >> @@ -158,7 +158,6 @@ config MULTICORE_RAID456
> >>         bool "RAID-4/RAID-5/RAID-6 Multicore processing (EXPERIMENTAL)"
> >>         depends on MD_RAID456
> >>         depends on SMP
> >> -       depends on EXPERIMENTAL
> >
> > In this case MULTICORE_RAID456 and the related code should go as
> > well... now that there are patches to supersede this implementation in
> > md-next.
> 
> Can my original patch go through as-is for Linus's tree? Right now,
> this is the last use of EXPERIMENTAL in v3.9-rc1. If we can drop it,
> we can remove the config item entirely from v3.9.

My pull request which removes CONFIG_MULTICORE_RAID456 completely was a little
late and missed -rc1.  Hopefully it will appear soon.
But if it isn't gone by -rc2, I have no objection to your patch going in then.

NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2013-03-04 21:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-23  7:40 [PATCH] md/raid456: remove depends on CONFIG_EXPERIMENTAL Kees Cook
2013-02-27  1:27 ` Dan Williams
2013-02-27  6:03   ` Kees Cook
2013-02-27 22:11   ` NeilBrown
2013-03-11 10:27     ` Paul Bolle
2013-03-12  1:36       ` NeilBrown
2013-03-04 18:59   ` Kees Cook
2013-03-04 21:11     ` NeilBrown [this message]
2013-03-04 21:13       ` Kees Cook

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=20130305081102.73211ef9@notabene.brown \
    --to=neilb@suse.de \
    --cc=agk@redhat.com \
    --cc=arjan@linux.intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=djbw@fb.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    /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).