From: Jakub Kicinski <kuba@kernel.org>
To: Jan Stancek <jstancek@redhat.com>
Cc: donald.hunter@gmail.com, pabeni@redhat.com, davem@davemloft.net,
edumazet@google.com, horms@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] tools: ynl: two patches to ease building with rpmbuild
Date: Mon, 11 Nov 2024 15:52:46 -0800 [thread overview]
Message-ID: <20241111155246.17aa0199@kernel.org> (raw)
In-Reply-To: <cover.1730976866.git.jstancek@redhat.com>
On Mon, 11 Nov 2024 14:04:43 +0100 Jan Stancek wrote:
> I'm looking to build and package ynl for Fedora and Centos Stream users.
Great to hear!
> Default rpmbuild has couple hardening options enabled by default [1][2],
> which currently prevent ynl from building.
Could you rebase on:
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/
and resend? I see some fuzz:
Applying: tools: ynl: add script dir to sys.path
Using index info to reconstruct a base tree...
M tools/net/ynl/cli.py
M tools/net/ynl/ynl-gen-c.py
Falling back to patching base and 3-way merge...
Auto-merging tools/net/ynl/ynl-gen-c.py
Auto-merging tools/net/ynl/cli.py
Applying: tools: ynl: extend CFLAGS to keep options from environment
With that fixed feel free to add to the patches:
Acked-by: Jakub Kicinski <kuba@kernel.org>
One thing I keep thinking about, maybe you already read this, is to
add some sort of spec search path and install the specs under /usr.
So the user can simply say --family X on the CLI without specifying
the fs full path to the YAML file. Would you be willing to send a patch
for this?
next prev parent reply other threads:[~2024-11-11 23:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 13:04 [PATCH 0/2] tools: ynl: two patches to ease building with rpmbuild Jan Stancek
2024-11-11 13:04 ` [PATCH 1/2] tools: ynl: add script dir to sys.path Jan Stancek
2024-11-11 13:04 ` [PATCH 2/2] tools: ynl: extend CFLAGS to keep options from environment Jan Stancek
2024-11-11 23:52 ` Jakub Kicinski [this message]
2024-11-12 8:16 ` [PATCH 0/2] tools: ynl: two patches to ease building with rpmbuild Jan Stancek
2024-11-12 9:26 ` Donald Hunter
2024-11-12 15:28 ` Jakub Kicinski
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=20241111155246.17aa0199@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jstancek@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).