All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: rpm@xenomai.org
Cc: adeos-main <adeos-main@gna.org>
Subject: Re: [Adeos-main] [PATCH 3/5] avoid naming conflict around __ipipe_irq_handler
Date: Sun, 30 Dec 2007 18:15:14 +0100	[thread overview]
Message-ID: <4777D222.7000904@domain.hid> (raw)
In-Reply-To: <4777770F.8060403@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]

Philippe Gerum wrote:
> Jan Kiszka wrote:
>> There is already a definition of __ipipe_irq_handler. So, we either need
>> to more the real ipipe_irq_handler_t into ipipe_base.h, or rename this
>> local variant to __ipipe_irq_handler_t, or simple drop this refactoring.
>> This patch starts with applying the latter - the easiest one :->
>>
> 
> There is no naming conflict, since they describe the same type with
> different even if close names on purpose. __ipipe_irq_handler is only a

Sorry for remaining unclear: I was referring to the __ipipe_irq_handler
helper macro from linux/ipipe.h. They may happen to live happily side by
side, but it is far from being clean.

> local short-hand to reduce visual pollution; as a matter of fact, the
> assembly code itself depends on the handler prototype, despite it cannot
> rely on any C-defined type, so the problem - if any - starts even before
> this local definition, and if you happen to change ipipe_irq_handler_t,
> then you could just not miss fixing __ipipe_irq_handler in the same move.
> 
> The only sane way to avoid defining this short-hand is indeed to move
> ipipe_irq_handler_t to linux/ipipe_base.h.
> 

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

      reply	other threads:[~2007-12-30 17:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-29 23:13 [Adeos-main] [PATCH 3/5] avoid naming conflict around __ipipe_irq_handler Jan Kiszka
2007-12-30 10:46 ` Philippe Gerum
2007-12-30 17:15   ` Jan Kiszka [this message]

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=4777D222.7000904@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=adeos-main@gna.org \
    --cc=rpm@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.