[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20140917182540.GG4723@linux.vnet.ibm.com>
Date: Wed, 17 Sep 2014 11:25:40 -0700
From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To: Paul Bolle <pebolle@...cali.nl>
Cc: Clark Williams <clark.williams@...il.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] rcu: unify boost and kthread priorities
On Wed, Sep 17, 2014 at 07:45:57PM +0200, Paul Bolle wrote:
> On Wed, 2014-09-17 at 10:17 -0700, Paul E. McKenney wrote:
> > On Wed, Sep 17, 2014 at 06:49:03PM +0200, Paul Bolle wrote:
> > > There's a reference to CONFIG_RCU_BOOST_PRIO in
> > > tools/testing/selftests/rcutorture/doc/TREE_RCU-kconfig.txt. It needs
> > > updating too, doesn't it?
> >
> > Good catch!
> >
> > Also the one in tools/testing/selftests/rcutorture/configs/rcu/TREE03.
>
> >From my local perl monstrosity:
> # ... and Paul McKenney's rcutorture stuff (v3.14-rc+)
> if ($blob->[1] =~ /tools\/testing\/selftests\/rcutorture\/configs\/.*/) {
>
> Ie, I've made that script ignore all references to Kconfig macros below
> tools/testing/selftest/rcutorture/configs. Is that too crude?
It would not hurt to check the files that appear in the CFLIST files:
tools/testing/selftests/rcutorture/configs/lock/CFLIST
tools/testing/selftests/rcutorture/configs/rcu/CFLIST
These files drive the torture-test kernel configurations.
That said, yes, there are sometimes some obsolete or deprecated
Kconfig parameters in these files because some systems need them.
Thanx, Paul
> > Fixed both, thank you!
>
>
> Paul Bolle
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists