cris port lacks a merge?

cris port lacks a merge?

[Adrian Bunk]

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

-- 

       "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

RE: cris port lacks a merge?

[Mikael Starvik]

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.

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

-- 

       "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

Re: cris port lacks a merge?

[Adrian Bunk]

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

Re: cris port lacks a merge?

[Roland Dreier]

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

One way to reduce your backlog might be to choose a small subset of
the most urgent out of all your pending patches -- say, the minimum
required to get cris working if it doesn't build/work in the latest
kernel, or the most urgent bug fixes if it does still work -- and then
update just that subset.  By reducing the number of patches, you can
reduce the amount of time in step 4 and reduce the chance of entering
step 5.

Then, once that batch is merged, move on to the next most urgent set
of patches, etc.

Also, creating a git tree might make the job of rebasing patches
easier, and also reduces the friction in getting Linus to merge your
patches.

 - R.