Messages in this thread | | | Date | Mon, 30 Jul 2007 12:51:46 +0200 | From | Adrian Bunk <> | Subject | Re: cris port lacks a merge? |
| |
On Mon, Jul 30, 2007 at 09:44:19AM +0200, Mikael Starvik wrote:
> I will make another try soon. > > The problem is that every time I try the following happens: > > 1. I download the bleeding edge latest stuff that you can get > 2. I prepare and submit patches > 3. I get replies with comments on my patches > 4. I fix the patches. > 5. I get told that the patches are against a too old version > 6. Repeat from 1. > > But I will continue to start making attempts to send patches upstreams > again.
Considering that your last merge was two years ago something goes wrong - and I suspect something goes wrong at 5.
If you download the latest -rc kernel at step 1 there should usually be no problem to let your patches Andrew add them to -mm and him forwarding them to Linus at the next merge window instead of running into point 5.
If there are conflicts with some bigger cross-architecture changes they should have been mentioned at 3.
I'll look at why it goes wrong when you submit your patches the next time.
> Patches are also available at http://developer.axis.com > > /Mikael > > -----Original Message----- > From: Adrian Bunk [mailto:bunk@stusta.de] > Sent: Sunday, July 15, 2007 2:04 PM > To: Mikael Starvik > Cc: dev-etrax; linux-kernel@vger.kernel.org > Subject: cris port lacks a merge? > > > Hi Mikael, > > the last maintainer update to arch/cris/ was two years ago and it seems > code like e.g. the config variable ETRAX_ARCH_V32 is missing. > > I assume there is there some external tree you use that contains updates? > If yes, can you submit the changes for inclusion into the upstream kernel? > > TIA > Adrian
cu Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
- 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/
| |