From: Jan Beulich <jbeulich@suse.com>
To: Christophe Lyon <christophe.lyon@linaro.org>
Cc: binutils@sourceware.org
Subject: Re: [PATCH] opcodes: Fix build verbosity
Date: Wed, 13 Mar 2024 08:38:38 +0100 [thread overview]
Message-ID: <37e92e02-12f1-48e9-8600-266e7c5264c3@suse.com> (raw)
In-Reply-To: <20240312164144.1142937-1-christophe.lyon@linaro.org>
On 12.03.2024 17:41, Christophe Lyon wrote:
> Add $(AM_V_xxx) in a few places where they were missing.
Okay.
Thanks, Jan
prev parent reply other threads:[~2024-03-13 7:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 16:41 Christophe Lyon
2024-03-13 7:38 ` Jan Beulich [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=37e92e02-12f1-48e9-8600-266e7c5264c3@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=christophe.lyon@linaro.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 read-only IMAP folder(s) and NNTP newsgroup(s).