From: Steve Dickson <SteveD@RedHat.com>
To: Petr Vorel <petr.vorel@gmail.com>
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>,
linux-nfs@vger.kernel.org, Mike Frysinger <vapier@gentoo.org>
Subject: Re: [nfs-utils PATCH 0/3] bump rpcgen version and silence some warning
Date: Fri, 17 Jan 2020 09:32:09 -0500 [thread overview]
Message-ID: <818c66c5-6f8b-927f-229e-52a00f50c682@RedHat.com> (raw)
In-Reply-To: <20200117063032.GA6351@dell5510>
Hey Petr,
On 1/17/20 1:30 AM, Petr Vorel wrote:
>>> 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.
>
> Giulio, thanks for your patch. I'll have a look on it over a weekend.
> Maybe Mike's cross-compilation patch is really not needed.
>
Thanks... for taking a second look!!
steved.
next prev parent reply other threads:[~2020-01-17 14:32 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
2020-01-17 6:30 ` Petr Vorel
2020-01-17 14:32 ` Steve Dickson [this message]
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=818c66c5-6f8b-927f-229e-52a00f50c682@RedHat.com \
--to=steved@redhat.com \
--cc=giulio.benetti@benettiengineering.com \
--cc=linux-nfs@vger.kernel.org \
--cc=petr.vorel@gmail.com \
--cc=vapier@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 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.