From: Jan Kiszka <jan.kiszka@domain.hid>
To: "oliver.schlenker@domain.hid" <oliver.schlenker@domain.hid>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Re-2: :: rt_printf with daemonized task
Date: Thu, 22 Oct 2009 18:34:10 +0200 [thread overview]
Message-ID: <4AE08982.8050501@domain.hid> (raw)
In-Reply-To: <0000AEB3.4ADF1568@domain.hid>
oliver.schlenker@domain.hid wrote:
> -------- Original Message --------
> Subject: Re: :: rt_printf with daemonized task (19-Okt-2009 16:00)
> From: Jan Kiszka <jan.kiszka@domain.hid>
> To: oliver.schlenker@domain.hid
>
>> If you move the definition of print_to_buffer right below this prototype
>> block, you would avoid having to add this prototype and you would have
>> likely generated a more reviewable patch. The large code movement below
>> is very hard to check regarding correctness as I do not see the actually
>> modified lines.
>
> Ok, moved back definition of print_to_buffer to avoid large code movement
>
>>> static void cleanup_buffer(struct print_buffer *buffer);
>>> static void print_buffers(void);
>>> +static void forked_child_init(void);
>> Stray prototype.
>
> deleted
>
>>>
>>> +void rt_syslog(int priority, char *format, ...)
>>> +{
>>> + va_list args;
>>> +
>>> + va_start(args, format);
>>> + print_to_buffer(RT_PRINT_SYSLOG_STREAM, priority, format, args);
>>> + va_end(args);
>>> +
>>> + return;
>> Unneeded return.
>
> Deleted
>
>>> +}
>>> +
>>> +void rt_vsyslog(int priority, char *format, va_list args )
>>> +{
>>> + print_to_buffer(RT_PRINT_SYSLOG_STREAM, priority, format, args);
>>> +
>>> + return;
>> Here too.
>
> Also deleted
>
>>> +}
>>> +
>>> static void set_buffer_name(struct print_buffer *buffer, const char *name)
>>> {
>>> int n;
>>>
>>>
>>> /* *** Deferred Output Management *** */
>>>
>>> +static int print_to_buffer(FILE *stream, int priority,
>>> + const char *format,va_list args)
>> When moving this function, please also indent this properly and take
>> care for a space after the ','.
>
> should be correct now.
>
>> Jan
>>
>> --
>> Siemens AG, Corporate Technology, CT SE 2
>> Corporate Competence Center Embedded Linux
>
>
> when patches are acked by you, should I do something with the patches
> like sending to a special mailing list or is it ok to have them posted in
> this list ?
I was about to apply them to my tree and send out a git pull request to
Philippe. Unfortunately I missed so far that your mail client or gateway
damaged the patch format seriously (the '@@' markers are all missing).
So if you have a clean "diff -up" of your changes, please sent them in a
tarball to me or via a proper mail client / account that keeps emails
intact. Otherwise I would have to reconstruct all changes by hand...
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2009-10-22 16:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 12:06 [Xenomai-help] Re-2: :: rt_printf with daemonized task oliver.schlenker
2009-10-22 16:34 ` Jan Kiszka [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-10-23 7:24 oliver.schlenker
2009-10-07 13:13 [Xenomai-help] Re-2: " oliver.schlenker
2009-10-07 13:16 ` Gilles Chanteperdrix
2009-10-07 13:38 ` Andreas Glatz
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=4AE08982.8050501@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=oliver.schlenker@domain.hid \
--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.