All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Philippe Gerum <rpm@xenomai.org>
Cc: adeos-main <adeos-main@gna.org>
Subject: [Adeos-main] fastcall and asmlinkage in x86
Date: Fri, 28 Dec 2007 15:18:13 +0100	[thread overview]
Message-ID: <477505A5.6070900@domain.hid> (raw)

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

Hi Philippe,

most of the code in arch/x86/ipipe_*.c can be pushed into some
ipipe-common.c, reducing the patch size by 10-20k and improving code
maintainability.

But one thing is currently blocking a copy&paste move: a lot of
functions that are declared fastcall on 32 bit are asmlinkage on 64 bit.
As both asmlinkage and fastcall are meaningless on 64 bit, can we safely
switch to fastcall? Or even better, could we drop that redundant
declarations totally, given that everything is fastcall on 32 bit anyway
(unless its marked asmlinkage)?

Thanks,
Jan


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

             reply	other threads:[~2007-12-28 14:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-28 14:18 Jan Kiszka [this message]
2007-12-28 15:43 ` [Adeos-main] fastcall and asmlinkage in x86 Philippe Gerum

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=477505A5.6070900@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.