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

[Robert L. <rm...@te...>]

On Sun, 2001-12-09 at 19:35, NIIBE Yutaka wrote:

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

True.

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

Good.

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

Excellent!  I'll be happy to help if needed; just let me know.

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

He is not me, but the DC drivers seem very solid.  2.4 _is) taking new
drivers so you can send those off.  We actually have a better chance of
getting the 2.4 merge synced ... 2.5 may take longer.

	Robert Love