DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Tomasz Duszynski <tduszynski@marvell.com>,
	Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dpdk-dev <dev@dpdk.org>, Jerin Jacob <jerinj@marvell.com>,
	 Jan Viktorin <viktorin@rehivetech.com>,
	Ruifeng Wang <ruifeng.wang@arm.com>,
	 Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH] config/arm: disable building octeontx2 on cn10k
Date: Fri, 8 Oct 2021 14:40:40 +0530	[thread overview]
Message-ID: <CALBAE1OKKDOcMZTJnJSnDR5M4y7MD8HZYzWO=yfB16uSw7u3wg@mail.gmail.com> (raw)
In-Reply-To: <20211001203833.2115176-1-tduszynski@marvell.com>

On Sat, Oct 2, 2021 at 2:09 AM Tomasz Duszynski <tduszynski@marvell.com> wrote:
>
> Common octeontx2 code shares some of the PCI identifiers
> with cn10k platform and if built wrong drivers may be probed.
>
> octeontx2 configuration disables common cn10k code so disable
> common octeontx2 on cn10k.
>
> Signed-off-by: Tomasz Duszynski <tduszynski@marvell.com>
> Reviewed-by: Jerin Jacob Kollanukkaran <jerinj@marvell.com>


Changed subject to config/cn10k: disable octeontx2 drivers

Applied to dpdk-next-net-mrvl/for-next-net. Thanks.

> ---
>  config/arm/arm64_cn10k_linux_gcc | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/config/arm/arm64_cn10k_linux_gcc b/config/arm/arm64_cn10k_linux_gcc
> index a3578c03a1..88e5f10945 100644
> --- a/config/arm/arm64_cn10k_linux_gcc
> +++ b/config/arm/arm64_cn10k_linux_gcc
> @@ -14,3 +14,4 @@ endian = 'little'
>
>  [properties]
>  platform = 'cn10k'
> +disable_drivers = 'common/octeontx2'
> --
> 2.25.1
>

      reply	other threads:[~2021-10-08  9:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-01 20:38 Tomasz Duszynski
2021-10-08  9:10 ` Jerin Jacob [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='CALBAE1OKKDOcMZTJnJSnDR5M4y7MD8HZYzWO=yfB16uSw7u3wg@mail.gmail.com' \
    --to=jerinjacobk@gmail.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jerinj@marvell.com \
    --cc=ruifeng.wang@arm.com \
    --cc=tduszynski@marvell.com \
    --cc=viktorin@rehivetech.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).