Re: [linuxsh-dev] Drop-In tree updates

[NIIBE Y. <gn...@m1...>]

Robert Love wrote:
 > However, a couple ideas: we need to realize that the above is a
 > 2.5-thing, and could take a _very_ long time to design, implement, test,
 > and finally have merged.  In the mean time, SH will grow further and
 > further out of sync.

Agreed.

 > (a) Don't send anything for mm/memory.c -- in our tree, keep it if'ed
 > out.  In the official tree, keep it as-is.  This means we keep the
 > reminder, we don't have the needless code, and the official tree doesn't
 > see anything yet.

For mm/memory.c, I think this is good.  Official tree works anyway, though
runs with bad performance.

 > (b) Implement the API for just that one file.  Something like:

Please look at Documentation/cachetlb.txt, we should add new routine here.

 > I understand.  What we disagree about is that we can't work around the
 > issue for the time-being.

No, I don't.  While I disagreed the handling of mm/memory.c, but I agree
that we should think and act for the synch to mainline.

 > Please consider the suggestions above.  Let's synchronize things as much
 > as possible.

Yes.

My plan for this week is like following:
	(1) Check the patches I hold, and check in to the repository:
		big-endian bug for users.h
		discontigous memory handling
		configuration issues (i.e., config.in and config.help)
	(2) Check the difference between 2.4 and repository
	    and send it to upstream.
	(3) Check the difference between 2.5 and repository
	    and send it to upstream.
	(4) Gather opinion and features for 2.5

For (2) or (3) I think that I will submit the difference to this list
before sending to upstream, so that people can see what's going on
more clearly.  Please note that I don't send all the difference, and
sometimes some parts may not be included by the upstream maintainer.

For (4), keeping up to kbuild is major one.

I have a question to M.R.  How do you think about the drivers for DC?
Is it ready for inclusion of mainline?  I don't know 2.4 opens for new
drivers or not, but at least it's worth sending those to 2.5. 
--