All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] [Xenomai-git] Jan Kiszka : cobalt/kernel: Remove unused mode parameter from COBALT_SYSCALL
Date: Fri, 17 Jul 2015 08:06:04 +0200	[thread overview]
Message-ID: <55A89B4C.7060008@siemens.com> (raw)
In-Reply-To: <20150716223406.GB16778@hermes.click-hack.org>

On 2015-07-17 00:34, Gilles Chanteperdrix wrote:
>> To explain the variation from your approach that you will find in my
>> queue now: Letting the script generate two files in one run is very
>> unhandy when defining the Makefile rules. So I now went for a two-stage
>> generation via awk that spits out two different macros the tables
>> can use.
> 
> Looks like nonsense to me. 

That's not necessary.

> 
> foo bar: foo.awk 
> 
> works with GNU make as far as I know
> 

Sure, but foo.awk is called only with foo or bar as target, so you can't
parametrize it and have to hard-code the outputs. Moreover, if running
parallel builds, make can decide to start both target generations at the
same time because it cannot see that running only one will already
magically generate the other.

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux


  reply	other threads:[~2015-07-17  6:06 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1ZAgI1-0000jO-Kb@sd-51317.xenomai.org>
2015-07-02 15:24 ` [Xenomai] [Xenomai-git] Jan Kiszka : cobalt/kernel: Remove unused mode parameter from COBALT_SYSCALL Philippe Gerum
2015-07-02 15:39   ` Jan Kiszka
2015-07-02 16:30     ` Philippe Gerum
2015-07-02 16:44       ` Jan Kiszka
2015-07-02 16:49         ` Gilles Chanteperdrix
2015-07-02 16:56           ` Philippe Gerum
2015-07-02 17:03             ` Gilles Chanteperdrix
2015-07-02 17:09               ` Philippe Gerum
2015-07-02 16:56           ` Gilles Chanteperdrix
2015-07-02 17:31             ` Jan Kiszka
2015-07-02 17:35               ` Gilles Chanteperdrix
2015-07-02 17:55                 ` Gilles Chanteperdrix
2015-07-02 17:57                   ` Jan Kiszka
2015-07-02 18:00                     ` Gilles Chanteperdrix
2015-07-02 18:42                     ` Gilles Chanteperdrix
2015-07-02 18:49                       ` Jan Kiszka
2015-07-02 18:55                         ` Gilles Chanteperdrix
2015-07-02 19:32                           ` Jan Kiszka
2015-07-02 20:26                             ` Jan Kiszka
2015-07-03 10:51                               ` Gilles Chanteperdrix
2015-07-03 12:31                                 ` Gilles Chanteperdrix
2015-07-03 12:38                                   ` Gilles Chanteperdrix
2015-07-16 12:35                                     ` Jan Kiszka
2015-07-16 18:42                                       ` Jan Kiszka
2015-07-16 22:34                                         ` Gilles Chanteperdrix
2015-07-17  6:06                                           ` Jan Kiszka [this message]
2015-07-17  7:23                                             ` Gilles Chanteperdrix
2015-07-16 12:34                                 ` Jan Kiszka

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=55A89B4C.7060008@siemens.com \
    --to=jan.kiszka@siemens.com \
    --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.