From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [PULL] rt-puts fix, mprotect testsuite
Date: Wed, 04 Apr 2012 15:12:20 +0200 [thread overview]
Message-ID: <4F7C48B4.8080006@domain.hid> (raw)
In-Reply-To: <4F7C4667.7010609@domain.hid>
On 2012-04-04 15:02, Gilles Chanteperdrix wrote:
> On 04/04/2012 02:56 PM, Jan Kiszka wrote:
>> The following changes since commit 0ef2410a2c9cf7102dead861241bd2d9957e4433:
>>
>> Mask signals in rt_print:printer_loop() (2012-04-02 00:16:41 +0200)
>>
>> are available in the git repository at:
>> git://git.xenomai.org/xenomai-jki.git for-upstream
>>
>> Jan Kiszka (3):
>> Append missing newline to rt_[f]puts output
>> testsuite: Add rt-print buffer flushes to native error paths
>
> As I said, I do not agree with calling rt_print_flush_buffers outside of
> xenomai libs.
rt_print_flush_buffers is a Xenomai API function that we export for
quite a while now. The rt_* functions are about explicit control when
what is invoked, both in the native skin and in what used to be rtdk.
Also, you can't avoid this function when you interact with libraries
that are unwrapped.
That said, I can fix that minor issue in leaks differently if you insist.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2012-04-04 13:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 12:56 [Xenomai-core] [PULL] rt-puts fix, mprotect testsuite Jan Kiszka
2012-04-04 13:02 ` Gilles Chanteperdrix
2012-04-04 13:12 ` Jan Kiszka [this message]
2012-04-04 13:23 ` Gilles Chanteperdrix
2012-04-04 13:38 ` Jan Kiszka
2012-04-15 16:48 ` Gilles Chanteperdrix
2012-04-15 17:09 ` Gilles Chanteperdrix
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F7C48B4.8080006@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.