From: Joe Damato <jdamato@fastly.com>
To: Donald Hunter <donald.hunter@gmail.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org,
"Jianfeng Liu" <liujianfeng1994@gmail.com>,
"Krzysztof Wilczy´nski" <kwilczynski@kernel.org>,
"Hao Luo" <haoluo@google.com>, "Tejun Heo" <tj@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tools/Makefile: Add ynl target
Date: Thu, 24 Apr 2025 09:42:07 -0700 [thread overview]
Message-ID: <aApp31D9sCcLQG50@LQ3V64L9R2> (raw)
In-Reply-To: <m2selxsw1t.fsf@gmail.com>
On Thu, Apr 24, 2025 at 11:17:34AM +0100, Donald Hunter wrote:
> Joe Damato <jdamato@fastly.com> writes:
>
> > Add targets to build, clean, and install ynl headers, libynl.a, and
> > python tooling.
> >
> > Signed-off-by: Joe Damato <jdamato@fastly.com>
> > ---
> > tools/Makefile | 16 +++++++++++++---
> > 1 file changed, 13 insertions(+), 3 deletions(-)
> >
> > diff --git a/tools/Makefile b/tools/Makefile
> > index 5e1254eb66de..c31cbbd12c45 100644
> > --- a/tools/Makefile
> > +++ b/tools/Makefile
> > @@ -41,6 +41,7 @@ help:
> > @echo ' mm - misc mm tools'
> > @echo ' wmi - WMI interface examples'
> > @echo ' x86_energy_perf_policy - Intel energy policy tool'
> > + @echo ' ynl - ynl headers, library, and python tool'
> > @echo ''
> > @echo 'You can do:'
> > @echo ' $$ make -C tools/ <tool>_install'
> > @@ -118,11 +119,14 @@ freefall: FORCE
> > kvm_stat: FORCE
> > $(call descend,kvm/$@)
> >
> > +ynl: FORCE
> > + $(call descend,net/ynl)
> > +
> > all: acpi counter cpupower gpio hv firewire \
> > perf selftests bootconfig spi turbostat usb \
> > virtio mm bpf x86_energy_perf_policy \
> > tmon freefall iio objtool kvm_stat wmi \
> > - debugging tracing thermal thermometer thermal-engine
> > + debugging tracing thermal thermometer thermal-engine ynl
> >
> > acpi_install:
> > $(call descend,power/$(@:_install=),install)
> > @@ -157,13 +161,16 @@ freefall_install:
> > kvm_stat_install:
> > $(call descend,kvm/$(@:_install=),install)
> >
> > +ynl_install:
> > + $(call descend,net/$(@:_install=),install)
>
> nit: I'm not sure there's any merit in the $(@:_install=) construct,
> when it's only really needed when there are multiple targets in the same
> rule. For ynl_install, $(call descend,net/ynl,install) would be just
> fine. It's funny that the existing convention in this Makefile is to
> mostly use substitution for the _install rules, but literals for the
> _clean rules.
That's right, I was trying to follow convention. I agree with what
you said. If the maintainer of whichever tree this goes into would
prefer that I re-spin this, I am happy to do so. I was mostly trying
to keep it consistent with the existing targets.
> Either way:
>
> Reviewed-by: Donald Hunter <donald.hunter@gmail.com>
Thanks!
next prev parent reply other threads:[~2025-04-24 16:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 20:46 [PATCH] tools/Makefile: Add ynl target Joe Damato
2025-04-24 10:17 ` Donald Hunter
2025-04-24 16:42 ` Joe Damato [this message]
2025-04-29 0:30 ` patchwork-bot+netdevbpf
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=aApp31D9sCcLQG50@LQ3V64L9R2 \
--to=jdamato@fastly.com \
--cc=bhelgaas@google.com \
--cc=donald.hunter@gmail.com \
--cc=haoluo@google.com \
--cc=kuba@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liujianfeng1994@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=tj@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