DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: David Marchand <david.marchand@redhat.com>
Cc: <dev@dpdk.org>, <mb@smartsharesystems.com>,
	Nicolas Chautru <nicolas.chautru@intel.com>,
	Gagandeep Singh <g.singh@nxp.com>,
	"Hemant Agrawal" <hemant.agrawal@nxp.com>,
	Elena Agostini <eagostini@nvidia.com>,
	Liron Himi <lironh@marvell.com>, Ori Kam <orika@nvidia.com>
Subject: Re: [PATCH] drivers: add dependencies for some classes
Date: Fri, 25 Aug 2023 18:17:36 +0100	[thread overview]
Message-ID: <ZOjiMLKzShhQahJU@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20230825170237.3829998-1-david.marchand@redhat.com>

On Fri, Aug 25, 2023 at 07:02:36PM +0200, David Marchand wrote:
> A few classes meson.build were not expressing dependencies to the
> associated device library. Define std_deps for baseband, gpu and regex
> drivers.
> 
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
>  drivers/baseband/acc/meson.build           | 2 +-
>  drivers/baseband/fpga_5gnr_fec/meson.build | 2 +-
>  drivers/baseband/fpga_lte_fec/meson.build  | 2 +-
>  drivers/baseband/la12xx/meson.build        | 2 +-
>  drivers/baseband/meson.build               | 2 ++
>  drivers/baseband/null/meson.build          | 2 +-
>  drivers/baseband/turbo_sw/meson.build      | 2 +-
>  drivers/gpu/cuda/meson.build               | 2 +-
>  drivers/gpu/meson.build                    | 2 ++
>  drivers/regex/cn9k/meson.build             | 2 +-
>  drivers/regex/meson.build                  | 2 +-
>  drivers/regex/mlx5/meson.build             | 2 +-
>  12 files changed, 14 insertions(+), 10 deletions(-)
> 
Acked-by: Bruce Richardson <bruce.richardson@intel.com>

  reply	other threads:[~2023-08-25 17:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25 17:02 [PATCH] drivers: add dependencies for some classes David Marchand
2023-08-25 17:17 ` Bruce Richardson [this message]
2023-08-25 18:18 ` Morten Brørup
2023-08-26  8:40   ` David Marchand
2023-08-28 19:38 ` Maxime Coquelin
2023-08-29  8:05 ` David Marchand

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=ZOjiMLKzShhQahJU@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=eagostini@nvidia.com \
    --cc=g.singh@nxp.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=lironh@marvell.com \
    --cc=mb@smartsharesystems.com \
    --cc=nicolas.chautru@intel.com \
    --cc=orika@nvidia.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