From: Petr Vorel <pvorel@suse.cz>
To: Steve Dickson <steved@redhat.com>
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH v3] nfsrahead: fix linking while static linking
Date: Tue, 13 Sep 2022 17:56:55 +0200 [thread overview]
Message-ID: <YyCoRz6FfHgnCnmw@pevik> (raw)
In-Reply-To: <42980d60-3b6d-4479-8c1a-a5fd7ba30f4c@redhat.com>
> 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)
Kind regards,
Petr
> > So for the moment it’s a decent solution indeed it’s been committed to
> > Buildroot
> > but I’ll try to improve it once I’ll have time.
> Sounds like a plan...
> steved.
> > Kind regards
> > —
> > Giulio Benetti
> > CEO/CTO@Benetti Engineering sas
> > > steved.
> > > > Thank you all.
> > > > Best regards
> > > > Giulio
> > > > > Kind regards,
> > > > > Petr
next prev parent reply other threads:[~2022-09-13 17:08 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 [this message]
2022-09-13 21:06 ` Giulio Benetti
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=YyCoRz6FfHgnCnmw@pevik \
--to=pvorel@suse.cz \
--cc=giulio.benetti@benettiengineering.com \
--cc=linux-nfs@vger.kernel.org \
--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 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.