[PATCH v3] Updating trace buffer configuration

--- linkers/rtld-trace-buffer.ini | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/linkers/rtld-trace-buffer.ini b/linkers/rtld-trace-buffer.ini index af9fc31..c17f2f1 100644 --- a/linkers/rtld-trace-buffer.ini +++ b/linkers/rtld-trace-buffer.ini @@ -26,6 +26,8 @@ buffer-l

Re: [PATCH] Updating trace buffer configuration

On 31/5/18 4:14 am, Sebastian Huber wrote: > - Am 30. Mai 2018 um 15:35 schrieb Amaan Cheval amaan.che...@gmail.com: > > [...] >> Minor, but in most other places in RTEMS, I've seen pointers declared >> with the asterisk on the variable not on the type ("int *ptr;" instead >> of "int* ptr;").

Re: [PATCH] Updating trace buffer configuration

On 31/5/18 1:35 am, Amaan Cheval wrote> Minor, but in most other places in RTEMS, I've seen pointers declared > with the asterisk on the variable not on the type ("int *ptr;" instead > of "int* ptr;"). I write code with the '*' on the type, after all it is an integer pointer (int* v;) and not a po

Re: [PATCH v2] tester: Add script to generate html coverage report from covoar output

On 2 June 2018 at 00:48, Joel Sherrill wrote: > > > On Fri, Jun 1, 2018, 11:21 AM Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> On 1 June 2018 at 20:30, Gedare Bloom wrote: >> >>> On Fri, Jun 1, 2018 at 10:28 AM, Vijay Kumar Banerjee >>> wrote: >>> > On 1 June 2018 at 19:24, Jo

Re: [PATCH v2] tester: Add script to generate html coverage report from covoar output

On Fri, Jun 1, 2018, 11:21 AM Vijay Kumar Banerjee wrote: > On 1 June 2018 at 20:30, Gedare Bloom wrote: > >> On Fri, Jun 1, 2018 at 10:28 AM, Vijay Kumar Banerjee >> wrote: >> > On 1 June 2018 at 19:24, Joel Sherrill wrote: >> >> >> >> >> >> >> >> On Fri, Jun 1, 2018 at 2:46 AM, Vijay Kumar B

(release notes generator) Code review for html parser

Dr. Joel and Chris, Thank you so much for the meeting on Wednesday! It really helps a lot. I have wrote three python class to get URL, ticket info and milestone info, can you review my code on github? (linke is attached below) Just want to know if I am on the right track, thank you! https://gith

Re: [PATCH v2] tester: Add script to generate html coverage report from covoar output

On 1 June 2018 at 20:30, Gedare Bloom wrote: > On Fri, Jun 1, 2018 at 10:28 AM, Vijay Kumar Banerjee > wrote: > > On 1 June 2018 at 19:24, Joel Sherrill wrote: > >> > >> > >> > >> On Fri, Jun 1, 2018 at 2:46 AM, Vijay Kumar Banerjee > >> wrote: > >>> > >>> Here's the list of Ideas for improvem

Re: [PATCH v2] tester: Add script to generate html coverage report from covoar output

On Fri, Jun 1, 2018 at 10:28 AM, Vijay Kumar Banerjee wrote: > On 1 June 2018 at 19:24, Joel Sherrill wrote: >> >> >> >> On Fri, Jun 1, 2018 at 2:46 AM, Vijay Kumar Banerjee >> wrote: >>> >>> Here's the list of Ideas for improvements: >>> >>> 1. Include the section coverage in the bsp config fil

Re: [PATCH v2] tester: Add script to generate html coverage report from covoar output

On 1 June 2018 at 19:24, Joel Sherrill wrote: > > > On Fri, Jun 1, 2018 at 2:46 AM, Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> Here's the list of Ideas for improvements: >> >> 1. Include the section coverage in the bsp config file. >> If the section is not found then the s

Re: [PATCH v2] tester: Add script to generate html coverage report from covoar output

On Fri, Jun 1, 2018 at 2:46 AM, Vijay Kumar Banerjee < vijaykumar9...@gmail.com> wrote: > Here's the list of Ideas for improvements: > > 1. Include the section coverage in the bsp config file. > If the section is not found then the script will show > proper error showing coverage is not su

Re: [PATCH v2] tester: Add script to generate html coverage report from covoar output

Here's the list of Ideas for improvements: 1. Include the section coverage in the bsp config file. If the section is not found then the script will show proper error showing coverage is not supported for the provided bsp config file. 2. Update covoar to add support for separate covera