From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Brian Masney <bmasney@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
aruiz@redhat.com
Subject: Re: [PATCH 0/2] tools/bootconfig: allow overriding CFLAGS and LDFLAGS
Date: Mon, 31 Mar 2025 21:23:37 +0900 [thread overview]
Message-ID: <20250331212337.3e9e4a5c50f5d3f16a95b120@kernel.org> (raw)
In-Reply-To: <20250328183858.1417835-1-bmasney@redhat.com>
On Fri, 28 Mar 2025 14:38:56 -0400
Brian Masney <bmasney@redhat.com> wrote:
> Allow the user to override the CFLAGS and LDFLAGS similar to what's
> currently done on other kernel tools. These changes allows bootconfig to
> be compiled with the hardened compiler and linker flags.
>
> Brian Masney (2):
> tools/bootconfig: allow overriding CFLAGS assignment
> tools/bootconfig: specify LDFLAGS as an argument to CC
>
Both looks good to me. Let me pick those up.
Thanks!
> tools/bootconfig/Makefile | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> --
> 2.47.0
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2025-03-31 12:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 18:38 [PATCH 0/2] tools/bootconfig: allow overriding CFLAGS and LDFLAGS Brian Masney
2025-03-28 18:38 ` [PATCH 1/2] tools/bootconfig: allow overriding CFLAGS assignment Brian Masney
2025-03-28 18:38 ` [PATCH 2/2] tools/bootconfig: specify LDFLAGS as an argument to CC Brian Masney
2025-03-31 12:23 ` Masami Hiramatsu [this message]
2025-04-10 15:36 ` [PATCH 0/2] tools/bootconfig: allow overriding CFLAGS and LDFLAGS Brian Masney
2025-05-16 2:25 ` Masami Hiramatsu
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=20250331212337.3e9e4a5c50f5d3f16a95b120@kernel.org \
--to=mhiramat@kernel.org \
--cc=aruiz@redhat.com \
--cc=bmasney@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.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).