All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: mingo@elte.hu, "eric.dumazet@gmail.com" <eric.dumazet@gmail.com>,
	tglx@linutronix.de, luca@luca-barbieri.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] ix86: adjust asm constraints in atomic64 wrappers
Date: Wed, 18 Jan 2012 09:25:14 -0800	[thread overview]
Message-ID: <4F17007A.9090102@zytor.com> (raw)
In-Reply-To: <4F1707F5020000780006D868@nat28.tlf.novell.com>

On 01/18/2012 08:57 AM, Jan Beulich wrote:
>>
>> For functions with nonstandard calling conventions it is normal to
>> declare them as void foo(void);
>
> For the above, I'd like to keep atomic64_t in the signature. Would
> void foo(atomic64_t, ...) be acceptable?
>

Sounds reasonable to me.  It doesn't matter much.

 >
 >> It may be a good idea to prefix these symbols with __ though.
 >
 > But not in this patch. (Can't resist to add that if you think it
 > should be this way, why did you not make it a condition for accepting
 > theoriginal patch, which you committed?)
 >

I didn't say "condition", I said "it may be a good idea".  Agreed in not 
in this patch.

The other bit in all of that is that, guess what, some people with solid 
track records, like yourself, I generally trust to do things mostly 
right, and so I don't actually scrutinize quite as in depth as I would 
patches from other people.  Every now and then it means I stumble upon 
something later after I have thought about it more.  This is by and 
large fine.

	-hpa

      reply	other threads:[~2012-01-18 17:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-18 14:22 [PATCH 1/2] ix86: adjust asm constraints in atomic64 wrappers Jan Beulich
2012-01-18 16:45 ` H. Peter Anvin
2012-01-18 16:57   ` Jan Beulich
2012-01-18 17:25     ` H. Peter Anvin [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=4F17007A.9090102@zytor.com \
    --to=hpa@zytor.com \
    --cc=JBeulich@suse.com \
    --cc=eric.dumazet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca@luca-barbieri.com \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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.