From: Steve Dickson <steved@redhat.com>
To: Sam James <sam@gentoo.org>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH v2] Fix more function prototypes
Date: Tue, 27 Sep 2022 10:09:26 -0400 [thread overview]
Message-ID: <d1e17fe0-947b-ccd1-44d2-bfa251f379f3@redhat.com> (raw)
In-Reply-To: <5C0273D4-1BC4-4B1A-BB6E-D16BA30113C3@gentoo.org>
On 9/25/22 12:10 AM, Sam James wrote:
>
>
>> On 16 Sep 2022, at 22:43, Sam James <sam@gentoo.org> wrote:
>>
>> ```
>> regex.c:545:43: error: a function declaration without a prototype is deprecated in all versions of C [-Werror,-Wstrict-prototypes]
>> struct trans_func *libnfsidmap_plugin_init()
>> ^
>> void
>> 1 error generated.
>> ```
>>
>> See: 167f2336b06e1bcbf26f45f2ddc4a535fed4d393
>> Signed-off-by: Sam James <sam@gentoo.org>
>> ---
>> support/nfsidmap/regex.c | 2 +-
>> utils/idmapd/idmapd.c | 2 +-
>> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> ping
Thanks! Committed!
steved.
prev parent reply other threads:[~2022-09-27 14:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 21:43 [PATCH v2] Fix more function prototypes Sam James
2022-09-25 4:10 ` Sam James
2022-09-27 14:09 ` Steve Dickson [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=d1e17fe0-947b-ccd1-44d2-bfa251f379f3@redhat.com \
--to=steved@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=sam@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).