All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Steve Dickson <SteveD@redhat.com>
Cc: linux-nfs@vger.kernel.org, Chuck Lever <chuck.lever@oracle.com>,
	libtirpc-devel@lists.sourceforge.net
Subject: Re: [Libtirpc-devel] [PATCHv2] src: remove use of the __P() macro
Date: Wed, 17 Aug 2016 16:32:00 +0200	[thread overview]
Message-ID: <20160817143200.GD5778@free.fr> (raw)
In-Reply-To: <4b788aa2-d8c5-b47c-e7ed-48a1e5824491@RedHat.com>

Steve, Chuck, Mike, All,

On 2016-08-17 10:26 -0400, Steve Dickson spake thusly:
> On 08/15/2016 04:49 PM, Yann E. MORIN wrote:
> > The __P() macro is a legacy compatibility macro aimed making pre-ANSI
> > (i.e. K&R) compilers that do not support function prototypes happy,
> > while still allowing such prototypes for ANSI-compliant compilers.
> > 
> > Since virtually all compilers have been ANSI-compliant for a few decades
> > now, use of __P() is totally useless.
> > 
> > Furthermore, __P() is defined in the non-standard sys/cdefs.h header.
> > This header is present in glibc and uClibc, and both have it included
> > from many of their headers. So, sys/cdefs.h is automagically included in
> > most cases and its macros are available.
> > 
> > However, the musl C library does not provide this sys/cdefs.h header.
> > Thus, the build breaks on musl.
> > 
> > For all the above reasons, get rid of __P() wherever it is used; just
> > always declare real function prototypes.
> > 
> > Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> > Cc: Chuck Lever <chuck.lever@oracle.com>
> > Cc: Steve Dickson <SteveD@redhat.com>
> > Cc: Mike Frysinger <vapier@gentoo.org>
> Committed... 

Thanks all for your reviews and suggestions! :-)

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

      reply	other threads:[~2016-08-17 14:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-15 20:49 [PATCHv2] src: remove use of the __P() macro Yann E. MORIN
2016-08-16  1:51 ` Chuck Lever
2016-08-17 14:26 ` [Libtirpc-devel] " Steve Dickson
2016-08-17 14:32   ` Yann E. MORIN [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=20160817143200.GD5778@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=SteveD@redhat.com \
    --cc=chuck.lever@oracle.com \
    --cc=libtirpc-devel@lists.sourceforge.net \
    --cc=linux-nfs@vger.kernel.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.