Re: Changed location for arm-lpae/for-next

Re: Changed location for arm-lpae/for-next

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 824 bytes --]

Hi Catalin,

On Tue, 4 Oct 2011 14:26:14 +0100 Catalin Marinas <catalin.marinas@arm.com> wrote:
>
> Since I don't know when I'll get my account back on kernel.org, I
> re-instated my tree on linux-arm.org. Could you please pull this tree
> instead of arm-lpae/for-next:
> 
>   git://linux-arm.org/linux-2.6.git for-next

OK, I have switched to that from today.  However, that site is also
inaccessible today :-(

> BTW, you could name it catalin/for-next or something else rather than
> arm-lpae as I have some kmemleak patches in there as well (I could split
> the patches in two branches if you'd prefer).

I would prefer that you split the kmemleak patches out into a separate
tree or branch.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

Re: Changed location for arm-lpae/for-next

[Catalin Marinas]

Hi Stephen,

On 5 October 2011 02:06, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> On Tue, 4 Oct 2011 14:26:14 +0100 Catalin Marinas <catalin.marinas@arm.com> wrote:
>>
>> Since I don't know when I'll get my account back on kernel.org, I
>> re-instated my tree on linux-arm.org. Could you please pull this tree
>> instead of arm-lpae/for-next:
>>
>>   git://linux-arm.org/linux-2.6.git for-next
>
> OK, I have switched to that from today.  However, that site is also
> inaccessible today :-(

Ah, sorry about that, some IT issues again (looks fine internally). If
you don't mind to change them again, I created two branches on github,
the first one for LPAE and the other for kmemleak:

git://github.com/cmarinas/linux.git for-next
git://github.com/cmarinas/linux.git kmemleak

Thanks.

-- 
Catalin

Re: Changed location for arm-lpae/for-next

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 2026 bytes --]

Hi Catlain,

On Wed, 5 Oct 2011 18:04:56 +0100 Catalin Marinas <catalin.marinas@arm.com> wrote:
>
> Ah, sorry about that, some IT issues again (looks fine internally). If
> you don't mind to change them again, I created two branches on github,
> the first one for LPAE and the other for kmemleak:
> 
> git://github.com/cmarinas/linux.git for-next

I have switched to that from today.

> git://github.com/cmarinas/linux.git kmemleak

And added that from today as well.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgment of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window. 

You will need to ensure that the patches/commits in your tree/series have
been:
     * submitted under GPL v2 (or later) and include the Contributor's
	Signed-off-by,
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and 
     * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

-- 
Cheers,
Stephen Rothwell 
sfr@canb.auug.org.au

Legal Stuff:
By participating in linux-next, your subsystem tree contributions are
public and will be included in the linux-next trees.  You may be sent
e-mail messages indicating errors or other issues when the
patches/commits from your subsystem tree are merged and tested in
linux-next.  These messages may also be cross-posted to the linux-next
mailing list, the linux-kernel mailing list, etc.  The linux-next tree
project and IBM (my employer) make no warranties regarding the linux-next
project, the testing procedures, the results, the e-mails, etc.  If you
don't agree to these ground rules, let me know and I'll remove your tree
from participation in linux-next.

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

Re: Changed location for arm-lpae/for-next

[Catalin Marinas]

Hi Stephen,

On 5 October 2011 23:56, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> On Wed, 5 Oct 2011 18:04:56 +0100 Catalin Marinas <catalin.marinas@arm.com> wrote:
>> I created two branches on github,
>> the first one for LPAE and the other for kmemleak:
>>
>> git://github.com/cmarinas/linux.git for-next
>
> I have switched to that from today.
>
>> git://github.com/cmarinas/linux.git kmemleak
>
> And added that from today as well.

I now got my kernel.org account back and I plan to remove the github
tree. You can get the above branches from:

git://git.kernel.org/pub/scm/linux/kernel/git/cmarinas/linux.git for-next
git://git.kernel.org/pub/scm/linux/kernel/git/cmarinas/linux.git kmemleak

(the first one contains the ARM LPAE patches)

Thanks.

-- 
Catalin

Re: Changed location for arm-lpae/for-next

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 525 bytes --]

Hi Catalin,

On Thu, 3 Nov 2011 10:29:24 +0000 Catalin Marinas <catalin.marinas@arm.com> wrote:
>
> I now got my kernel.org account back and I plan to remove the github
> tree. You can get the above branches from:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/cmarinas/linux.git for-next
> git://git.kernel.org/pub/scm/linux/kernel/git/cmarinas/linux.git kmemleak

OK, I have switched back to these.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]