From: Roberto Sassu <roberto.sassu@huaweicloud.com>
To: acme@kernel.org
Cc: peterz@infradead.org, mingo@redhat.com,
Jiri Olsa <olsajiri@gmail.com>,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
namhyung@kernel.org, quentin@isovalent.com,
linux-perf-users@vger.kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org,
Roberto Sassu <roberto.sassu@huawei.com>
Subject: Re: [PATCH 3/3] tools/build: Display logical OR of a feature flavors
Date: Tue, 27 Sep 2022 09:14:34 +0200 [thread overview]
Message-ID: <75986095d7ada2b24784ef356abc6ce17307575d.camel@huaweicloud.com> (raw)
In-Reply-To: <64352c51c5dcbab389201a16733f3157a1ea591e.camel@huaweicloud.com>
On Mon, 2022-08-22 at 13:24 +0200, Roberto Sassu wrote:
> On Mon, 2022-08-22 at 12:58 +0200, Jiri Olsa wrote:
> > On Thu, Aug 18, 2022 at 02:09:57PM +0200,
>
> [...]
>
> > > In verbose mode, of if no group is defined for a feature, show
> > > the
> > > feature
> > > detection result as before.
>
> Thanks Jiri.
>
> 'or' instead of 'of', if the patch can be edited.
Hi Arnaldo
will you take these patches?
Thanks
Roberto
next prev parent reply other threads:[~2022-09-27 7:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 12:09 [PATCH 1/3] tools/build: Fix feature detection output due to eval expansion roberto.sassu
2022-08-18 12:09 ` [PATCH 2/3] tools/build: Increment room for feature name in feature detection output roberto.sassu
2022-08-18 12:09 ` [PATCH 3/3] tools/build: Display logical OR of a feature flavors roberto.sassu
2022-08-18 13:09 ` Arnaldo Carvalho de Melo
2022-08-18 13:25 ` Roberto Sassu
2022-08-18 16:40 ` Quentin Monnet
2022-08-18 18:14 ` Arnaldo Carvalho de Melo
2022-08-18 22:15 ` Quentin Monnet
2022-08-22 10:58 ` Jiri Olsa
2022-08-22 11:24 ` Roberto Sassu
2022-09-27 7:14 ` Roberto Sassu [this message]
2022-09-27 12:21 ` Arnaldo Carvalho de Melo
2022-09-27 12:25 ` Roberto Sassu
2022-09-27 13:24 ` Quentin Monnet
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=75986095d7ada2b24784ef356abc6ce17307575d.camel@huaweicloud.com \
--to=roberto.sassu@huaweicloud.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=bpf@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=olsajiri@gmail.com \
--cc=peterz@infradead.org \
--cc=quentin@isovalent.com \
--cc=roberto.sassu@huawei.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;
as well as URLs for NNTP newsgroup(s).