Hi,
On Thu, Nov 11, 2010 at 11:32 AM, Anand Gadiyar wrote:
[...]
>> On Thu, Nov 11, 2010 at 5:59 AM, Nicolas Pitre
>> wrote:
>>> Now that the Linaro release is shipping with a 2.6.35 kernel, we need to
>>> move forward. I therefore created a linux-linaro-2.6.36 tree which
>>> contains the v2.6
On 11/11/2010 4:55 PM, Dave Martin wrote:
> Hi,
>
> On Thu, Nov 11, 2010 at 5:59 AM, Nicolas Pitre
> wrote:
>> Now that the Linaro release is shipping with a 2.6.35 kernel, we need to
>> move forward. I therefore created a linux-linaro-2.6.36 tree which
>> contains the v2.6.36 core code but wit
On 11/11/2010 11:29 AM, Nicolas Pitre wrote:
> Now that the Linaro release is shipping with a 2.6.35 kernel, we need to
> move forward. I therefore created a linux-linaro-2.6.36 tree which
> contains the v2.6.36 core code but with the latest ARM specific pieces
> from mainline.
>
> This branch
Hi,
On Thu, Nov 11, 2010 at 5:59 AM, Nicolas Pitre wrote:
> Now that the Linaro release is shipping with a 2.6.35 kernel, we need to
> move forward. I therefore created a linux-linaro-2.6.36 tree which
> contains the v2.6.36 core code but with the latest ARM specific pieces
> from mainline.
Do
Now that the Linaro release is shipping with a 2.6.35 kernel, we need to
move forward. I therefore created a linux-linaro-2.6.36 tree which
contains the v2.6.36 core code but with the latest ARM specific pieces
from mainline.
This branch is meant to be stable i.e. it won't be rebased, and only
