From: Steve Dickson <SteveD@RedHat.com>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: linux-nfs@vger.kernel.org, Petr Vorel <petr.vorel@gmail.com>
Subject: Re: [nfs-utils PATCH 0/3] bump rpcgen version and silence some warning
Date: Thu, 16 Jan 2020 16:08:30 -0500 [thread overview]
Message-ID: <c1e96762-0f3a-b465-da1b-f7bc7a687948@RedHat.com> (raw)
In-Reply-To: <6fdcbba5-e965-fe69-569b-7f32005ce1bf@benettiengineering.com>
On 1/16/20 3:44 PM, Giulio Benetti wrote:
> On 1/16/20 9:41 PM, Giulio Benetti wrote:
>> On 1/16/20 9:37 PM, Steve Dickson wrote:
>>>
>>>
>>> On 1/13/20 11:29 AM, Giulio Benetti wrote:
>>>> Giulio Benetti (3):
>>>> rpcgen: bump to latest version
>>>> rpcgen: rpc_cout: silence format-nonliteral
>>>> support: nfs: rpc_socket: silence unused parameter warning on salen
>>>>
>>>> support/nfs/rpc_socket.c | 2 +
>>>> tools/rpcgen/Makefile.am | 24 +-
>>>> tools/rpcgen/proto.h | 65 ++
>>>> tools/rpcgen/rpc_clntout.c | 458 +++++---
>>>> tools/rpcgen/rpc_cout.c | 1269 ++++++++++++----------
>>>> tools/rpcgen/rpc_hout.c | 915 +++++++++-------
>>>> tools/rpcgen/rpc_main.c | 2083 +++++++++++++++++++++---------------
>>>> tools/rpcgen/rpc_parse.c | 1055 +++++++++---------
>>>> tools/rpcgen/rpc_parse.h | 103 +-
>>>> tools/rpcgen/rpc_sample.c | 465 ++++----
>>>> tools/rpcgen/rpc_scan.c | 812 +++++++-------
>>>> tools/rpcgen/rpc_scan.h | 91 +-
>>>> tools/rpcgen/rpc_svcout.c | 1647 +++++++++++++++-------------
>>>> tools/rpcgen/rpc_tblout.c | 265 ++---
>>>> tools/rpcgen/rpc_util.c | 656 ++++++------
>>>> tools/rpcgen/rpc_util.h | 170 ++-
>>>> tools/rpcgen/rpcgen.1 | 442 ++++++++
>>>> 17 files changed, 6123 insertions(+), 4399 deletions(-)
>>>> create mode 100644 tools/rpcgen/proto.h
>>>> create mode 100644 tools/rpcgen/rpcgen.1
>>>>
>>> Committed... (tag nfs-utils-2-4-3-rc5)... Nice work!!!
>>
>> Wooho! Thank you :-)
>>
>> As soon as you release version 2.4.3 I'm going to bump version in
>> Buildroot too, at the moment it's still 1.3.4.
>
> Ah, I've forgot that on xtensa it fails building and need this patch to be applied to:
> https://patchwork.kernel.org/patch/11335261/
>
> If you have the chance to commit before releasing version it would be great!
Your patch on my radar... but... conflicts with Petr's cross-compilation patch
https://lore.kernel.org/linux-nfs/20200114183603.GA24556@dell5510/T/#t
That patch causes an automake warnings which is something I'm trying to avoid.
No worries... I will not do a release w/out your patch.... or something close to it.
steved.
next prev parent reply other threads:[~2020-01-16 21:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 16:29 [nfs-utils PATCH 0/3] bump rpcgen version and silence some warning Giulio Benetti
2020-01-13 16:29 ` [nfs-utils PATCH 2/3] rpcgen: rpc_cout: silence format-nonliteral Giulio Benetti
2020-01-13 16:29 ` [nfs-utils PATCH 3/3] support: nfs: rpc_socket: silence unused parameter warning on salen Giulio Benetti
2020-01-16 20:37 ` [nfs-utils PATCH 0/3] bump rpcgen version and silence some warning Steve Dickson
2020-01-16 20:41 ` Giulio Benetti
2020-01-16 20:44 ` Giulio Benetti
2020-01-16 21:08 ` Steve Dickson [this message]
2020-01-17 6:30 ` Petr Vorel
2020-01-17 14:32 ` Steve Dickson
2020-01-19 18:45 ` Petr Vorel
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=c1e96762-0f3a-b465-da1b-f7bc7a687948@RedHat.com \
--to=steved@redhat.com \
--cc=giulio.benetti@benettiengineering.com \
--cc=linux-nfs@vger.kernel.org \
--cc=petr.vorel@gmail.com \
/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).