From: Steven Rostedt <rostedt@goodmis.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Chun-Tse Shao <ctshao@google.com>,
devicetree@vger.kernel.org, frowand.list@gmail.com,
jpoimboe@redhat.com, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, masahiroy@kernel.org,
michal.lkml@markovi.net, peterz@infradead.org,
robh+dt@kernel.org
Subject: Re: [PATCH v2] config: Allow kernel installation packaging to override pkg-config
Date: Thu, 3 Mar 2022 07:42:43 -0500 [thread overview]
Message-ID: <20220303074243.29ca40c2@rorschach.local.home> (raw)
In-Reply-To: <CAKwvOdkWcu5ZPADGieb1Vb+kTbfHNzFAa3FXTWC98xXtzuLwqQ@mail.gmail.com>
On Wed, 2 Mar 2022 13:48:01 -0800
Nick Desaulniers <ndesaulniers@google.com> wrote:
> I'm ok with this patch; a quick grep though shows a few more open
> coded instances of pkg-config. Should we fix those up, too? i.e.
>
> certs/Makefile:92:HOSTCFLAGS_extract-cert.o = $(shell pkg-config
> --cflags libcrypto 2> /dev/null)
> certs/Makefile:93:HOSTLDLIBS_extract-cert = $(shell pkg-config --libs
> libcrypto 2> /dev/null || echo -lcrypto)
> scripts/kconfig/gconf-cfg.sh
For this patch set, the above is probably good enough to do (and test
with a make allmodconfig).
> tools/perf/Makefile.perf
> tools/ in general
I would hold off on doing tools for a separate patch. With the
exception of objtool most of tools is not needed for the build process.
-- Steve
next prev parent reply other threads:[~2022-03-03 12:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 23:06 [PATCH] config: Using HOSTPKG_CONFIG prefix for pkg-config Chun-Tse Shao
2022-03-02 14:18 ` Rob Herring
2022-03-02 15:27 ` Steven Rostedt
2022-03-02 19:36 ` [PATCH v2] config: Allow kernel installation packaging to override pkg-config Chun-Tse Shao
2022-03-02 21:48 ` Nick Desaulniers
2022-03-03 12:42 ` Steven Rostedt [this message]
2022-03-03 18:41 ` Nick Desaulniers
2022-03-03 23:50 ` [PATCH v3] " Chun-Tse Shao
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=20220303074243.29ca40c2@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=ctshao@google.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.org \
--cc=robh+dt@kernel.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).