Messages in this thread | | | Date | Mon, 28 Aug 2006 17:28:10 -0700 | From | Andrew Morton <> | Subject | Re: [PATCH 0/4] RCU: various merge candidates |
| |
On Tue, 29 Aug 2006 05:53:02 +0530 Dipankar Sarma <dipankar@in.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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |