Hi Mike,

your patch is just a cleanup and definitely not mission-critical.

Please wait until your needed environment emerges in Dave's net-2.6 or
net-next-2.6 tree until you post your patch for the specific tree then.

This makes it much easier - at least for Dave.

Thanks,
Oliver



-----Ursprüngliche Nachricht-----
Von: Mike Frysinger [mailto:[email protected]] 
Gesendet: Freitag, 19. März 2010 07:35
An: David Miller
Cc: [email protected]; [email protected]; 
[email protected]; Hartkopp, Oliver (K-EFFI/P); 
Thuermann, Urs, Dr. (K-EFFI/I)
Betreff: Re: [Uclinux-dist-devel] [PATCH] can: bfin_can: switch to common 
Blackfin can header

On Wed, Mar 17, 2010 at 01:51, David Miller wrote:
> From: Mike Frysinger <[email protected]>
>> if the next tree is merged into linux-next, then the header is already there
>
> One of the highest priority trees in -next is net-next-2.6,
> because so much other stuff ends up depending upon it.
>
> Therefore I keep it building independently, so no matter what Stephen
> Rothwell does the build isn't likely to break.
>
> Just get your stuff merged properly to Linus then resubmit
> your patch.

Linus has pulled my tree, so there shouldnt be any reason to not merge
this patch now
-mike
_______________________________________________
Socketcan-core mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/socketcan-core

Reply via email to