From: Kevin Traynor <ktraynor@redhat.com>
To: Kevin Traynor <ktraynor@redhat.com>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [18.11 0/7] Build fixes for 18.11 branch
Date: Mon, 13 Jan 2020 16:16:42 +0000 [thread overview]
Message-ID: <cfed0485-6526-f92d-1957-a829117316c3@redhat.com> (raw)
In-Reply-To: <20200109133433.12494-1-ktraynor@redhat.com>
On 09/01/2020 13:34, Kevin Traynor wrote:
> Fixes for various build configurations.
>
> Ali Alnubani (1):
> net/mlx: fix build with clang 9
>
> ^ what it says
>
> Kevin Traynor (2):
> kni: fix ethtool build for gcc 9
> pmdinfogen: fix freebsd build
>
> ^ 18.11 branch specific
>
> Stephen Hemminger (3):
> eal: drop unused macros for primary process check
> eventdev: use same log macro for all unsupported calls
> eal: remove legacy PMD log macro
>
> ^ Removes unused code that was causing build failure with clang 9
>
> Thomas Monjalon (1):
> net/mlx: allow build only on Linux
>
> ^ As libmnl requirement was removed, mlx4 build was being attempted on FreeBSD with meson
>
> Ali Alnubani (1):
> net/mlx: fix build with clang 9
>
> Kevin Traynor (2):
> kni: fix ethtool build for gcc 9
> pmdinfogen: fix freebsd build
>
> Stephen Hemminger (3):
> eal: drop unused macros for primary process check
> eventdev: use same log macro for all unsupported calls
> eal: remove legacy PMD log macro
>
> Thomas Monjalon (1):
> net/mlx: allow build only on Linux
>
> buildtools/pmdinfogen/meson.build | 5 ++
> drivers/net/mlx4/meson.build | 11 +++-
> drivers/net/mlx4/mlx4_utils.h | 5 +-
> drivers/net/mlx5/meson.build | 10 +++-
> drivers/net/mlx5/mlx5_utils.h | 5 +-
> kernel/linux/kni/ethtool/igb/e1000_82575.c | 3 +-
> kernel/linux/kni/ethtool/igb/e1000_mbx.c | 1 +
> kernel/linux/kni/ethtool/igb/e1000_phy.c | 1 +
> kernel/linux/kni/ethtool/igb/igb_ethtool.c | 4 ++
> kernel/linux/kni/ethtool/igb/igb_main.c | 4 ++
> kernel/linux/kni/ethtool/igb/igb_param.c | 1 +
> kernel/linux/kni/ethtool/ixgbe/ixgbe_82599.c | 2 +
> kernel/linux/kni/ethtool/ixgbe/ixgbe_common.c | 1 +
> .../linux/kni/ethtool/ixgbe/ixgbe_ethtool.c | 1 +
> kernel/linux/kni/ethtool/ixgbe/ixgbe_main.c | 4 ++
> lib/librte_eal/common/include/rte_dev.h | 56 +------------------
> lib/librte_eventdev/rte_eventdev.c | 4 +-
> 17 files changed, 54 insertions(+), 64 deletions(-)
>
Will push tomorrow if there are no objections.
next prev parent reply other threads:[~2020-01-13 16:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 13:34 Kevin Traynor
2020-01-09 13:34 ` [dpdk-stable] [18.11 1/7] eal: drop unused macros for primary process check Kevin Traynor
2020-01-09 13:34 ` [dpdk-stable] [18.11 2/7] eventdev: use same log macro for all unsupported calls Kevin Traynor
2020-01-09 13:34 ` [dpdk-stable] [18.11 3/7] eal: remove legacy PMD log macro Kevin Traynor
2020-01-09 13:34 ` [dpdk-stable] [18.11 4/7] net/mlx: fix build with clang 9 Kevin Traynor
2020-01-09 13:34 ` [dpdk-stable] [18.11 5/7] kni: fix ethtool build for gcc 9 Kevin Traynor
2020-01-09 13:34 ` [dpdk-stable] [18.11 6/7] pmdinfogen: fix freebsd build Kevin Traynor
2020-01-09 15:50 ` Neil Horman
2020-01-09 15:53 ` Neil Horman
2020-01-09 16:53 ` Kevin Traynor
2020-01-09 13:34 ` [dpdk-stable] [18.11 7/7] net/mlx: allow build only on Linux Kevin Traynor
2020-01-13 16:16 ` Kevin Traynor [this message]
2020-01-14 14:29 ` [dpdk-stable] [18.11 0/7] Build fixes for 18.11 branch Kevin Traynor
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=cfed0485-6526-f92d-1957-a829117316c3@redhat.com \
--to=ktraynor@redhat.com \
--cc=stable@dpdk.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 NNTP newsgroup(s).