Re: [rtems commit] bsp/motorola_powerpc: Fix for Binutils 2.28+

2017-06-01 Thread Sebastian Huber
- Am 2. Jun 2017 um 7:16 schrieb Chris Johns chr...@rtems.org: > On 02/06/2017 15:11, Sebastian Huber wrote: >> Module:rtems >> Branch:master >> Commit:7203b70be0266cdb4830537dfc8fd6189851708c >> Changeset: >>

Re: [rtems commit] bsp/motorola_powerpc: Fix for Binutils 2.28+

2017-06-01 Thread Chris Johns
On 02/06/2017 15:11, Sebastian Huber wrote: > Module:rtems > Branch:master > Commit:7203b70be0266cdb4830537dfc8fd6189851708c > Changeset: > http://git.rtems.org/rtems/commit/?id=7203b70be0266cdb4830537dfc8fd6189851708c > > Author:Sebastian Huber

[PATCH 2/2] implementation of inttypes.h and test related to its methods

2017-06-01 Thread Aditya Upadhyay
From: aadit0402 --- cpukit/Makefile.am | 1 + cpukit/configure.ac | 1 + cpukit/inttypes/Makefile.am | 14 +++ cpukit/inttypes/imaxabs.c| 40 + cpukit/inttypes/imaxdiv.c

[PATCH] implementation of inttypes.h and test related to its methods

2017-06-01 Thread aadit0402
--- cpukit/Makefile.am | 1 + cpukit/configure.ac | 1 + cpukit/inttypes/Makefile.am | 14 +++ cpukit/inttypes/imaxabs.c| 40 + cpukit/inttypes/imaxdiv.c| 50 +++

Re: Building RISC-V BSP

2017-06-01 Thread Denis Obrezkov
So, am I understand right, that I should make my repo, submit commits to it, produce patches and send them to your repo as pool requests? And should I make my repo by cloning yours? 2017-06-02 2:02 GMT+03:00 Hesham Almatary : > Hi Denis, > > On Fri, Jun 2, 2017 at 1:27

[PATCH v4 2/2] User Manual: Added ini format in rtems-tester

2017-06-01 Thread Tanu Hari Dixit
Added specification for ini format for configuration files in documentation of rtems-tester --- user/tools/tester.rst | 134 ++ 1 file changed, 134 insertions(+) diff --git a/user/tools/tester.rst b/user/tools/tester.rst index ae8c3b6..966a373

[PATCH v4] User Manual: Added rtems-tester in the docs

2017-06-01 Thread Tanu Hari Dixit
Added as part of Tools. Made changes according to Chris' review Also removed the ini format part inline with the new release that is expected. --- user/tools/index.rst | 1 + user/tools/tester.rst | 446 ++ 2 files changed, 447 insertions(+)

[PATCH 1/2] rtems-docs/user/../quick.rst: Fix typo, hard coded path, code layout.

2017-06-01 Thread Cillian O'Donnell
--- user/start/quick.rst | 15 --- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/user/start/quick.rst b/user/start/quick.rst index 47597af..8fc24f1 100644 --- a/user/start/quick.rst +++ b/user/start/quick.rst @@ -15,9 +15,9 @@ You need to have your development host set

[PATCH 2/2] docs/rsb/quick-start.rst: Fix typos, hard coded paths, version

2017-06-01 Thread Cillian O'Donnell
--- rsb/quick-start.rst | 242 ++-- 1 file changed, 121 insertions(+), 121 deletions(-) diff --git a/rsb/quick-start.rst b/rsb/quick-start.rst index f39c0a6..387ab61 100644 --- a/rsb/quick-start.rst +++ b/rsb/quick-start.rst @@ -42,13 +42,13 @@

[PATCH 0/2] *** Docs Update ***

2017-06-01 Thread Cillian O'Donnell
*** Just to note the rsb quick-start is all updated except for the output of --list-bsets because my setup only ever finds output for ../bare/config and not ../source-builder/config so I left that bit out just in case. Maybe someone else can update that section to 4.12. *** Cillian O'Donnell

Re: Building RISC-V BSP

2017-06-01 Thread Denis Obrezkov
Hello Hesham, should I apply your patches? or should I paste all of them to some directory (rsb has several 'patches' folders). Also, could you describe our workflow? In the context of with what repository I should work and where I should direct my pull requests. 2017-06-01 5:09 GMT+03:00

Re: RTEMS cfg of uncrustify

2017-06-01 Thread Sichen Zhao
Ok, i see. Thank you. Best Regards Sichen Zhao From: ged...@gwmail.gwu.edu on behalf of Gedare Bloom Sent: Thursday, June 1, 2017 23:14 To: Joel Sherrill Cc: Sichen Zhao; RTEMS Subject: Re: RTEMS cfg of

Re: RTEMS cfg of uncrustify

2017-06-01 Thread Gedare Bloom
On Thu, Jun 1, 2017 at 11:09 AM, Joel Sherrill wrote: > > > On Thu, Jun 1, 2017 at 9:07 AM, Sichen Zhao wrote: >> >> Hi all, >> >> The rtems cfg file of uncrustify: >> https://devel.rtems.org/wiki/Developer/Coding/Conventions#Tools >> I feel weird about :

Re: RTEMS cfg of uncrustify

2017-06-01 Thread Joel Sherrill
On Thu, Jun 1, 2017 at 9:07 AM, Sichen Zhao wrote: > Hi all, > > The rtems cfg file of uncrustify: https://devel.rtems.org/wiki/ > Developer/Coding/Conventions#Tools > I feel weird about : there are always space after and before the > parenthesis. It seems has conflict

RTEMS cfg of uncrustify

2017-06-01 Thread Sichen Zhao
Hi all, The rtems cfg file of uncrustify: https://devel.rtems.org/wiki/Developer/Coding/Conventions#Tools I feel weird about : there are always space after and before the parenthesis. It seems has conflict with Linux kernel tools checkpatch.pl rule Best Regards Sichen Zhao

Re: RFC: Any Outstanding Issues Before Branching 4.12?

2017-06-01 Thread Joel Sherrill
On Thursday, June 1, 2017, Chris Johns wrote: > On 01/06/2017 16:43, Joel Sherrill wrote: > > Hi > > > > Once the recent tool switch to gcc 7.1 has settled, I know of no major > > outstanding issues holding back branching 4.12. > > > > If anyone has items they consider critical

Re: RFC: Any Outstanding Issues Before Branching 4.12?

2017-06-01 Thread Chris Johns
On 01/06/2017 16:43, Joel Sherrill wrote: > Hi > > Once the recent tool switch to gcc 7.1 has settled, I know of no major > outstanding issues holding back branching 4.12. > > If anyone has items they consider critical to resolve before branching or > releasing 4.12.0, please speak up ASAP.

RFC: Any Outstanding Issues Before Branching 4.12?

2017-06-01 Thread Joel Sherrill
Hi Once the recent tool switch to gcc 7.1 has settled, I know of no major outstanding issues holding back branching 4.12. If anyone has items they consider critical to resolve before branching or releasing 4.12.0, please speak up ASAP. Otherwise, we will be moving tickets to either the next