---
cpukit/libfs/src/dosfs/msdos_format.c | 93 +--
1 file changed, 46 insertions(+), 47 deletions(-)
diff --git a/cpukit/libfs/src/dosfs/msdos_format.c
b/cpukit/libfs/src/dosfs/msdos_format.c
index 42f1d74575..326040f004 100644
---
On 1/10/19 3:50 pm, Sebastian Huber wrote:
> On 01/10/2019 01:40, Chris Johns wrote:
>> On 30/9/19 10:45 pm, Sebastian Huber wrote:
>>> ---
>>> images/user/patch-review.png | Bin 0 -> 57130 bytes
>>> images/user/patch-review.puml | 44 +++
>>>
On 01/10/2019 09:22, Chris Johns wrote:
On 1/10/19 3:50 pm, Sebastian Huber wrote:
On 01/10/2019 01:40, Chris Johns wrote:
On 30/9/19 10:45 pm, Sebastian Huber wrote:
[...]
+* The patch builds. All RTEMS tests link with this patch.
+
+* The patch does not introduce new compiler warnings.
Add support for _SMP_Send_message() to the own processor. This is
required by the smpmulticast01 test program.
---
bsps/sparc/erc32/start/bspsmp.c | 84
c/src/lib/libbsp/sparc/erc32/Makefile.am | 3 +-
2 files changed, 85 insertions(+), 2 deletions(-)
The double call of the timecounter get method was added to FreeBSD in
2002 without a comment. It is not clear why this is needed.
---
cpukit/score/src/kern_tc.c| 2 +-
testsuites/sptests/sptimecounter01/init.c | 12 ++--
2 files changed, 7 insertions(+), 7 deletions(-)
---
cpukit/include/sys/timetc.h | 4 +++-
cpukit/score/src/kern_tc.c| 10 +++---
testsuites/sptests/sptimecounter01/init.c | 4 ++--
3 files changed, 12 insertions(+), 6 deletions(-)
diff --git a/cpukit/include/sys/timetc.h b/cpukit/include/sys/timetc.h
index
This makes it possible to install higher quality timecounter in
plug-and-play systems and helps to override the clock driver provided
timecounter in some test scenarios.
---
cpukit/score/src/kern_tc.c| 2 +
testsuites/sptests/sptimecounter01/init.c | 101
This ensures that lines are output atomically if they are produced by
different other contexts, e.g. interrupts, other processors, other
threads.
Update #3199.
---
cpukit/include/t.h | 2 +
cpukit/libtest/t-test.c| 138 ++---
From: Mikail Yayla
---
testsuites/libtests/ttest01/test-assert.c | 21 +
testsuites/libtests/ttest01/test-checks.c | 2503 +
testsuites/libtests/ttest01/test-destructor.c |7 +
testsuites/libtests/ttest01/test-eno.c| 20 +
Update #3199.
---
testsuites/libtests/Makefile.am | 15 +
testsuites/libtests/ttest01/init.c| 54 +-
testsuites/libtests/ttest01/test-assert.c | 90 +
testsuites/libtests/ttest01/test-checks.c | 2914 +
On Fri, Mar 22, 2019 at 3:20 AM Sebastian Huber
wrote:
>
> This is an example test using the RTEMS Test Framework. It tests also
> the framework itself.
>
> Add T_FILE_NAME command line define to get rid of the full file path.
> This is important to reduce the read-only data of test files and
On Tue, Oct 1, 2019 at 3:53 PM Gedare Bloom wrote:
>
> On Wed, Sep 4, 2019 at 3:36 PM Martin Erik Werner
> wrote:
> >
> > Remove various incorrect references to "lock" and "obtain" and to an
> > option set which is not part of the barrier interface.
> >
> > It looks like the barrier
On Wed, Sep 4, 2019 at 3:36 PM Martin Erik Werner
wrote:
>
> Remove various incorrect references to "lock" and "obtain" and to an
> option set which is not part of the barrier interface.
>
> It looks like the barrier documentation was started based on a copy of
> the semaphore documentation and
On Tue, Oct 1, 2019, 5:07 PM Gedare Bloom wrote:
> On Tue, Oct 1, 2019 at 3:53 PM Gedare Bloom wrote:
> >
> > On Wed, Sep 4, 2019 at 3:36 PM Martin Erik Werner
> > wrote:
> > >
> > > Remove various incorrect references to "lock" and "obtain" and to an
> > > option set which is not part of the
On Tue, Oct 1, 2019 at 11:09 AM Martin Erik Werner
wrote:
>
> Remove the unfinished sentence
> "Since a barrier is, by definition, never immediately [...]"
> and jump directly to
> "The task may wait [forever or for a timeout]"
> instead.
>
> I cannot figure out what the unfinished sentence is
On Tue, Oct 1, 2019, 5:04 PM Gedare Bloom wrote:
> On Tue, Oct 1, 2019 at 11:09 AM Martin Erik Werner
> wrote:
> >
> > Remove the unfinished sentence
> > "Since a barrier is, by definition, never immediately [...]"
> > and jump directly to
> > "The task may wait [forever or for a timeout]"
> >
On 01/10/2019 23:40, Gedare Bloom wrote:
+/*
+ * SPDX-License-Identifier: BSD-2-Clause
+ * SPDX-License-Identifier: CC-BY-SA-4.0
+ *
+ * Copyright (C) 2018, 2019 embedded brains GmbH
+ *
+ * Redistribution and use in source and binary forms, with or without
+ * modification, are permitted
Remove various incorrect references to "lock" and "obtain" and to an
option set which is not part of the barrier interface.
It looks like the barrier documentation was started based on a copy of
the semaphore documentation and these things are surviving remnants.
Also remove an unfinished
Remove the unfinished sentence
"Since a barrier is, by definition, never immediately [...]"
and jump directly to
"The task may wait [forever or for a timeout]"
instead.
I cannot figure out what the unfinished sentence is supposed to be -
"released"? "passed"?
---
c-user/barrier_manager.rst | 7
Hi,
I'm re-sending this patch set since I received no reply previously (2019-09-04).
Martin Erik Werner (2):
barrier: Remove leftover semaphore remnants
barrier: Remove unfinished sentence
c-user/barrier_manager.rst | 45 ++---
1 file changed, 10
20 matches
Mail list logo
