On Fri, Mar 13, 2015 at 8:38 PM, Chris Johns wrote:
> On 14/03/2015 12:30 am, Gedare Bloom wrote:
>>
>> I would like to consider landing the drvmgr and pci patch-set as a
>> sparc-specific feature (e.g. only included in builds for sparc.)
>
>
> How is this controlled or are you saying we state in
On 14/03/2015 12:30 am, Gedare Bloom wrote:
I would like to consider landing the drvmgr and pci patch-set as a
sparc-specific feature (e.g. only included in builds for sparc.)
How is this controlled or are you saying we state in the release notes
this is only currently tested on SPARC BSPs ?
On March 13, 2015 8:30:46 AM CDT, Gedare Bloom wrote:
>On Fri, Mar 13, 2015 at 1:04 AM, Chris Johns wrote:
>> On 11/03/2015 1:33 am, Amar Takhar wrote:
>>>
>>> Can we come up with a plan for branching 4.11?
>>>
>>> We need to push off any commits made that are unrelated to tickets
>open in
>>>
On Fri, Mar 13, 2015 at 1:04 AM, Chris Johns wrote:
> On 11/03/2015 1:33 am, Amar Takhar wrote:
>>
>> Can we come up with a plan for branching 4.11?
>>
>> We need to push off any commits made that are unrelated to tickets open in
>> milestone 4.11 to the next release. This way any changes we make
On 13/03/15 06:04, Chris Johns wrote:
1. We need a suitable newlib snapshot to reference.
I have one pending Newlib patch, so the March snapshot would be nice.
This gives us two weeks from now to commit everything Newlib related.
--
Sebastian Huber, embedded brains GmbH
Address : Dornier
On 11/03/2015 1:33 am, Amar Takhar wrote:
Can we come up with a plan for branching 4.11?
We need to push off any commits made that are unrelated to tickets open in
milestone 4.11 to the next release. This way any changes we make have a narrow
scope.
This close to the release we should really b
