From: Giulio Benetti <giulio.benetti@benettiengineering.com>
To: Petr Vorel <pvorel@suse.cz>, Steve Dickson <steved@redhat.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH v3] nfsrahead: fix linking while static linking
Date: Tue, 13 Sep 2022 23:06:38 +0200 [thread overview]
Message-ID: <f67c4131-0dc0-a909-e5ad-d323406ce03d@benettiengineering.com> (raw)
In-Reply-To: <YyCoRz6FfHgnCnmw@pevik>
Hi Petr, Steve, All,
On 13/09/22 17:56, Petr Vorel wrote:
>
>
>> On 8/22/22 4:33 PM, Giulio Benetti wrote:
>>> Hi Steve, Petr,
>
>>> On 22/08/22 21:17, Steve Dickson wrote:
>
>
>>>> On 8/11/22 4:36 PM, Giulio Benetti wrote:
>>>>> Hi Petr,
>
>>>>>> Il giorno 11 ago 2022, alle ore 22:20, Petr Vorel
>>>>>> <pvorel@suse.cz> ha scritto:
>
>>>>>> Hi,
>
>>>>>> Reviewed-by: Petr Vorel <pvorel@suse.cz>
>
>>>>>> nit (not worth of reposting): I'm not a native speaker, but
>>>>>> IMHO subject should
>>>>>> be without while, e.g. "fix order on static linking"
>
>>>>> Totally, it sounds awful as it is now.
>>>>> I ask maintainers if it’s possible to reword like Petr
>>>>> pointed.
>>>> Will do!
>
>>> Thank you!
>
>>> I will try to improve the pkg-config autotools because as it is now it
>>> works but it’s not a good solution.
>
>>> I should use what it’s been suggested to me here:
>>> https://lists.buildroot.org/pipermail/buildroot/2022-August/648926.html
>>> And I’ve given another solution:
>>> https://lists.buildroot.org/pipermail/buildroot/2022-August/648933.html
>>> but it’s still not ok:
>>> https://lists.buildroot.org/pipermail/buildroot/2022-August/649058.html
>> I don't have access to those list...
>
> Yep, these are forbidden 403.
> Giulio, please post a link on lore
> https://lore.kernel.org/buildroot/
> (or on patchwork)
Oops, you're both right, thank you Petr.
Follows lore links:
I should use what it’s been suggested to me here:
https://lore.kernel.org/buildroot/20220810231839.1b6164f7@windsurf/
And I’ve given another solution:
https://lore.kernel.org/buildroot/20220810215104.107714-1-giulio.benetti@benettiengineering.com/
but it’s still not ok:
https://lore.kernel.org/buildroot/20220811224752.1a1e53b7@windsurf/
Best regards
--
Giulio Benetti
Benetti Engineering sas
next prev parent reply other threads:[~2022-09-13 21:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 22:12 [PATCH] nfsrahead: fix linking while static linking Giulio Benetti
2022-08-09 22:23 ` Giulio Benetti
2022-08-09 22:33 ` [PATCH v2] " Giulio Benetti
2022-08-10 21:43 ` Giulio Benetti
2022-08-10 21:45 ` [PATCH v3] " Giulio Benetti
2022-08-11 20:20 ` Petr Vorel
2022-08-11 20:36 ` Giulio Benetti
2022-08-22 19:17 ` Steve Dickson
2022-08-22 20:33 ` Giulio Benetti
2022-09-13 15:55 ` Steve Dickson
2022-09-13 15:56 ` Petr Vorel
2022-09-13 21:06 ` Giulio Benetti [this message]
2022-09-13 17:38 ` Steve Dickson
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=f67c4131-0dc0-a909-e5ad-d323406ce03d@benettiengineering.com \
--to=giulio.benetti@benettiengineering.com \
--cc=linux-nfs@vger.kernel.org \
--cc=pvorel@suse.cz \
--cc=steved@redhat.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