Re: Near Last Call Before Branching 4.11

2015-07-16 Thread Peter Dufault
> On Jul 16, 2015, at 15:07 , Joel Sherrill wrote: > >> >> - I was having NFS crashes regularly. I removed a pthread_mutex_trylock() >> in an ISR (I assumed that was safe) while trying to make that ISR faster and >> the NFS issues disappeared. I haven’t had time to go back to that either. >

Re: Near Last Call Before Branching 4.11

2015-07-16 Thread Joel Sherrill
On 7/16/2015 1:59 PM, Peter Dufault wrote: On Jul 16, 2015, at 13:55 , Joel Sherrill wrote: I am in the middle of a build sweep now with the tms570 patches and my bsp.h changes. Once this finishes, I plan to push those changes and cut the branch. Speak now. I have a two concerns but they

Re: Near Last Call Before Branching 4.11

2015-07-16 Thread Peter Dufault
> On Jul 16, 2015, at 13:55 , Joel Sherrill wrote: > > I am in the middle of a build sweep now with the tms570 patches > and my bsp.h changes. Once this finishes, I plan to push those > changes and cut the branch. > > Speak now. I have a two concerns but they’ll have to be fixed after the bran

Near Last Call Before Branching 4.11

2015-07-16 Thread Joel Sherrill
Hi I am in the middle of a build sweep now with the tms570 patches and my bsp.h changes. Once this finishes, I plan to push those changes and cut the branch. Speak now. -- Joel Sherrill, Ph.D. Director of Research & Development joel.sherr...@oarcorp.comOn-Line Applications R

Branching 4.11 Tomorrow

2015-07-14 Thread Joel Sherrill
Hi I plan to cut the branch tomorrow. This will provide some time for folks to test on the branch and get any last minute fixes in. I plan to let the branch sit for until the week of July 27 before I cut 4.11.0. This is because I will be in Hastings UK next week and don't want to do this while

Re: Branching 4.11

2015-03-13 Thread Gedare Bloom
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

Re: Branching 4.11

2015-03-13 Thread Chris Johns
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 ?

Re: Branching 4.11

2015-03-13 Thread Joel Sherrill
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 commit

Re: Branching 4.11

2015-03-13 Thread Gedare Bloom
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

Re: Branching 4.11

2015-03-13 Thread Sebastian Huber
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

Re: Branching 4.11

2015-03-12 Thread Chris Johns
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

Branching 4.11

2015-03-10 Thread Amar Takhar
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 be in a slush period then a hard close