From: Peter Korsgaard <peter@korsgaard.com>
To: James Knight <james.d.knight@live.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/5] package/rpm: drop remnants of custom CFLAGS
Date: Thu, 08 Jun 2023 22:39:25 +0200 [thread overview]
Message-ID: <87ilbx3czm.fsf@48ers.dk> (raw)
In-Reply-To: <SN4P221MB0682A85E1D08A44BED847C8EA0709@SN4P221MB0682.NAMP221.PROD.OUTLOOK.COM> (James Knight's message of "Sun, 7 May 2023 17:34:29 -0400")
>>>>> "James" == James Knight <james.d.knight@live.com> writes:
> Drops the use of `RPM_CFLAGS`, which their use has been obsolete when
> this package bumped to v4.17 [1].
> [1]: 429e247b869027f6ecd4efa0f31bccd2765e3875
> Signed-off-by: James Knight <james.d.knight@live.com>
> ---
> Changes v1 -> v2:
> - This patch has been split across multiple patches; no changes to the
> implementation itself (suggested by Yann E. MORIN)
Committed to 2023.02.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-06-08 20:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-07 21:34 [Buildroot] [PATCH v2 1/5] package/rpm: drop remnants of custom CFLAGS James Knight
2023-05-07 21:47 ` Yann E. MORIN
2023-06-08 20:39 ` Peter Korsgaard [this message]
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=87ilbx3czm.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=james.d.knight@live.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