linux-kernel - Re: [PATCH 0/4] RCU: various merge candidates

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20060828172810.00081afa.akpm@osdl.org>
Date:	Mon, 28 Aug 2006 17:28:10 -0700
From:	Andrew Morton <akpm@...l.org>
To:	dipankar@...ibm.com
Cc:	Alan Stern <stern@...land.harvard.edu>,
	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	Paul E McKenney <paulmck@...ibm.com>
Subject: Re: [PATCH 0/4] RCU: various merge candidates

On Tue, 29 Aug 2006 05:53:02 +0530
Dipankar Sarma <dipankar@...ibm.com> wrote:

> > >
> > > rcutorture fix patches independent of rcu implementation changes
> > > in this patchset.
> > 
> > So this patchset is largely orthogonal to the presently-queued stuff?
> 
> Yes, it should be.

OK.

> > > > Now what?
> > > 
> > > Heh. I can always re-submit against -mm after I wait for a day or two
> > > for comments :)
> > 
> > That would be good, thanks.  We were seriously considering merging all the
> > SRCU stuff for 2.6.18, because
> 
> I think non-srcu rcutorture patches can be merged in 2.6.19. srcu
> is a tossup. Perhaps srcu and this patchset may be merge candidates
> for 2.6.20 should things go well in review and testing.

Oh.  I was planning on merging *rcu* into 2.6.19-rc1.

> Should I re-submit
> against 2.6.18-mm1 or so (after your patchset reduces in size) ?
> What is a convenient time ?

Any time..

> GAh! cpufreq.

heh.
-
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/