From: patchwork-bot+netdevbpf@kernel.org
To: Jan Stancek <jstancek@redhat.com>
Cc: donald.hunter@gmail.com, kuba@kernel.org, pabeni@redhat.com,
davem@davemloft.net, edumazet@google.com, horms@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] tools: ynl: two patches to ease building with rpmbuild
Date: Thu, 14 Nov 2024 02:50:44 +0000 [thread overview]
Message-ID: <173155264423.1461768.15559112771408021687.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1731399562.git.jstancek@redhat.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 12 Nov 2024 09:21:31 +0100 you wrote:
> I'm looking to build and package ynl for Fedora and Centos Stream users.
> Default rpmbuild has couple hardening options enabled by default [1][2],
> which currently prevent ynl from building.
>
> This series contains 2 small patches to address it.
>
> [1] https://fedoraproject.org/wiki/Changes/Harden_All_Packages
> [2] https://fedoraproject.org/wiki/Changes/PythonSafePath
>
> [...]
Here is the summary with links:
- [v2,1/2] tools: ynl: add script dir to sys.path
https://git.kernel.org/netdev/net-next/c/c3b3eb565bd7
- [v2,2/2] tools: ynl: extend CFLAGS to keep options from environment
https://git.kernel.org/netdev/net-next/c/05a318b4fc13
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-11-14 2:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 8:21 [PATCH v2 0/2] tools: ynl: two patches to ease building with rpmbuild Jan Stancek
2024-11-12 8:21 ` [PATCH v2 1/2] tools: ynl: add script dir to sys.path Jan Stancek
2024-11-12 9:34 ` Donald Hunter
2024-11-12 8:21 ` [PATCH v2 2/2] tools: ynl: extend CFLAGS to keep options from environment Jan Stancek
2024-11-12 9:35 ` Donald Hunter
2024-11-14 2:50 ` patchwork-bot+netdevbpf [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=173155264423.1461768.15559112771408021687.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jstancek@redhat.com \
--cc=kuba@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.