On Tue, Mar 23, 2021 at 9:57 AM Joel Sherrill wrote:
>
>
>
> On Tue, Mar 23, 2021 at 10:49 AM Sebastian Huber
> wrote:
>>
>> Hello Alex,
>>
>> this file has little in common with the RTEMS coding style. This is
>> quite understandable since the style is very exotic. I don't think we
>> will have
On Tue, Mar 23, 2021 at 10:49 AM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> Hello Alex,
>
> this file has little in common with the RTEMS coding style. This is
> quite understandable since the style is very exotic. I don't think we
> will have a formatting tool which is able to
Hello Alex,
this file has little in common with the RTEMS coding style. This is
quite understandable since the style is very exotic. I don't think we
will have a formatting tool which is able to produce the RTEMS style in
the near future. This gives raise to some general questions.
1. Do we
On Mon, Mar 22, 2021 at 3:32 PM Alex White wrote:
>
> ---
> .../aarch64/aarch64-exception-frame-print.c | 105 +-
> 1 file changed, 101 insertions(+), 4 deletions(-)
>
> diff --git a/cpukit/score/cpu/aarch64/aarch64-exception-frame-print.c
> b/cpukit/score/cpu/aarch64/aarch64-e
---
.../aarch64/aarch64-exception-frame-print.c | 105 +-
1 file changed, 101 insertions(+), 4 deletions(-)
diff --git a/cpukit/score/cpu/aarch64/aarch64-exception-frame-print.c
b/cpukit/score/cpu/aarch64/aarch64-exception-frame-print.c
index 59b5d06032..348151a468 100644
--- a
