From: Raslan Darawsheh <rasland@nvidia.com>
To: Ali Alnubani <alialnu@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "bruce.richardson@intel.com" <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH] common/mlx5: fix glue library name
Date: Sun, 1 Nov 2020 13:07:31 +0000 [thread overview]
Message-ID: <DM6PR12MB274854BC90F93D0C651D8625CF130@DM6PR12MB2748.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20201026092035.11461-2-alialnu@nvidia.com>
Hi,
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Ali Alnubani
> Sent: Monday, October 26, 2020 11:21 AM
> To: dev@dpdk.org
> Cc: bruce.richardson@intel.com
> Subject: [dpdk-dev] [PATCH] common/mlx5: fix glue library name
>
> The MLX5 glue library wasn't following the standard
> 'librte_<class>_<name>.so' naming.
>
> Fixes: a20b2c01a7a1 ("build: standardize component names and defines")
> Cc: bruce.richardson@intel.com
>
> Signed-off-by: Ali Alnubani <alialnu@nvidia.com>
> ---
> drivers/common/mlx5/linux/meson.build | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/common/mlx5/linux/meson.build
> b/drivers/common/mlx5/linux/meson.build
> index 9ef8e181d..0d437f8fb 100644
> --- a/drivers/common/mlx5/linux/meson.build
> +++ b/drivers/common/mlx5/linux/meson.build
> @@ -5,7 +5,7 @@ includes += include_directories('.')
> 2.28.0
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
next prev parent reply other threads:[~2020-11-01 13:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 9:20 [dpdk-dev] [PATCH] net/mlx4: " Ali Alnubani
2020-10-26 9:20 ` [dpdk-dev] [PATCH] common/mlx5: " Ali Alnubani
2020-11-01 10:35 ` Matan Azrad
2020-11-01 13:07 ` Raslan Darawsheh [this message]
2020-10-28 7:42 ` [dpdk-dev] [PATCH] net/mlx4: " Matan Azrad
2020-11-01 11:49 ` Raslan Darawsheh
2020-11-02 13:01 ` Ferruh Yigit
2020-11-02 13:04 ` Ferruh Yigit
2020-11-02 13:04 ` Ali Alnubani
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=DM6PR12MB274854BC90F93D0C651D8625CF130@DM6PR12MB2748.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=alialnu@nvidia.com \
--cc=bruce.richardson@intel.com \
--cc=dev@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).