All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Pavan Nikhilesh <pbhagavatula@marvell.com>
Cc: dev <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>,
	 Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Subject: Re: [dpdk-dev] [PATCH 21.11 v2 0/3] octeontx build only on 64-bit Linux
Date: Tue, 17 Aug 2021 10:46:14 +0200	[thread overview]
Message-ID: <CAJFAV8xz46AGa+jrPpn_fd7L_PTeLZLOcrUEm1GwNpf2+4TbFg@mail.gmail.com> (raw)
In-Reply-To: <20210325145209.2000195-1-thomas@monjalon.net>

On Thu, Mar 25, 2021 at 3:52 PM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> This is a reorg of the patches from Pavan.
> It has been discussed that it should wait for DPDK 21.11
> for ABI compatibility reason.
>
> Pavan Nikhilesh (3):
>   net/thunderx: enable build only on 64-bit Linux
>   common/octeontx: enable build only on 64-bit Linux
>   common/octeontx2: enable build only on 64-bit Linux
>
>  drivers/common/octeontx/meson.build   |  6 ++++++
>  drivers/common/octeontx2/meson.build  |  4 ++--
>  drivers/compress/octeontx/meson.build |  6 ++++++
>  drivers/crypto/octeontx/meson.build   |  7 +++++--
>  drivers/event/octeontx/meson.build    |  6 ++++++
>  drivers/event/octeontx2/meson.build   |  4 ++--
>  drivers/mempool/octeontx/meson.build  |  5 +++--
>  drivers/mempool/octeontx2/meson.build |  9 ++-------
>  drivers/net/octeontx/meson.build      |  4 ++--
>  drivers/net/octeontx2/meson.build     | 10 ++--------
>  drivers/net/thunderx/meson.build      |  4 ++--
>  drivers/raw/octeontx2_dma/meson.build | 10 ++++++----
>  12 files changed, 44 insertions(+), 31 deletions(-)

There were a couple of cleanups (indent etc..) and changes in meson files.
This series does not apply cleanly on the main branch.
Could you rebase it?

I noticed that the net/cnxk driver does not have this check, but it is
disabled anyway since it depends on common/cnxk.
Is it worth adding the check for consistency?


-- 
David Marchand


  parent reply	other threads:[~2021-08-17  8:47 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-25 17:02 [dpdk-dev] [PATCH 1/7] common/octeontx: enable build only on 64bit Linux pbhagavatula
2021-02-25 17:02 ` [dpdk-dev] [PATCH 2/7] mempool/octeontx: " pbhagavatula
2021-02-25 17:02 ` [dpdk-dev] [PATCH 3/7] net/octeontx: " pbhagavatula
2021-02-25 17:02 ` [dpdk-dev] [PATCH 4/7] crypto/octeontx: " pbhagavatula
2021-02-25 17:02 ` [dpdk-dev] [PATCH 5/7] event/octeontx: " pbhagavatula
2021-02-25 17:02 ` [dpdk-dev] [PATCH 6/7] raw/octeontx2: enable build only for " pbhagavatula
2021-03-22 15:14   ` Radha Mohan
2021-02-25 17:02 ` [dpdk-dev] [PATCH 7/7] compress/octeontx: " pbhagavatula
2021-02-26  5:52   ` Ashish Gupta
2021-03-24 10:55 ` [dpdk-dev] [PATCH 1/7] common/octeontx: enable build only on " Jerin Jacob
2021-03-25 10:42   ` Thomas Monjalon
2021-03-25 10:46     ` Thomas Monjalon
2021-03-25 10:58       ` Kinsella, Ray
2021-03-25 11:03         ` Thomas Monjalon
2021-03-25 12:46           ` Jerin Jacob
2021-03-25 12:47             ` Kinsella, Ray
2021-03-25 12:58               ` Jerin Jacob
2021-03-25 13:02                 ` Kinsella, Ray
2021-03-26 10:50                   ` Jerin Jacob
2021-03-25 14:57             ` Thomas Monjalon
2021-03-25 15:01               ` David Marchand
2021-03-25 14:52 ` [dpdk-dev] [PATCH 21.11 v2 0/3] octeontx build only on 64-bit Linux Thomas Monjalon
2021-03-25 14:52   ` [dpdk-dev] [PATCH 21.11 v2 1/3] net/thunderx: enable " Thomas Monjalon
2021-08-23 19:54     ` [dpdk-dev] [PATCH v3 " pbhagavatula
2021-08-23 19:54       ` [dpdk-dev] [PATCH v3 2/3] common/octeontx: " pbhagavatula
2021-08-23 19:54       ` [dpdk-dev] [PATCH v3 3/3] common/octeontx2: " pbhagavatula
2021-09-07 12:14       ` [dpdk-dev] [PATCH v3 1/3] net/thunderx: " Ferruh Yigit
2021-10-03 20:36       ` [dpdk-dev] [PATCH v4 " pbhagavatula
2021-10-03 20:36         ` [dpdk-dev] [PATCH v4 2/3] common/octeontx: " pbhagavatula
2021-10-03 20:36         ` [dpdk-dev] [PATCH v4 3/3] common/octeontx2: " pbhagavatula
2021-10-04  5:56         ` [dpdk-dev] [PATCH v5 1/3] net/thunderx: " pbhagavatula
2021-10-04  5:56           ` [dpdk-dev] [PATCH v5 2/3] common/octeontx: " pbhagavatula
2021-10-04  5:56           ` [dpdk-dev] [PATCH v5 3/3] common/octeontx2: " pbhagavatula
2021-10-04  9:05           ` [dpdk-dev] [PATCH v5 1/3] net/thunderx: " Ferruh Yigit
2021-10-14 19:56           ` [dpdk-dev] [PATCH v6 " pbhagavatula
2021-10-14 19:56             ` [dpdk-dev] [PATCH v6 2/3] common/octeontx: " pbhagavatula
2021-10-18  7:03               ` Harman Kalra
2021-10-14 19:56             ` [dpdk-dev] [PATCH v6 3/3] common/octeontx2: " pbhagavatula
2021-10-15 10:39             ` [dpdk-dev] [PATCH v6 1/3] net/thunderx: " Ferruh Yigit
2021-10-15 13:58               ` [dpdk-dev] [EXT] " Pavan Nikhilesh Bhagavatula
2021-10-15 16:32                 ` Ferruh Yigit
2021-10-15 17:16             ` [dpdk-dev] " Ferruh Yigit
2021-03-25 14:52   ` [dpdk-dev] [PATCH 21.11 v2 2/3] common/octeontx: " Thomas Monjalon
2021-03-25 14:52   ` [dpdk-dev] [PATCH 21.11 v2 3/3] common/octeontx2: " Thomas Monjalon
2021-08-17  8:46   ` David Marchand [this message]
2021-08-21 14:07 [dpdk-dev] [PATCH 21.11 v2 0/3] octeontx " Pavan Nikhilesh Bhagavatula

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=CAJFAV8xz46AGa+jrPpn_fd7L_PTeLZLOcrUEm1GwNpf2+4TbFg@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=pbhagavatula@marvell.com \
    --cc=thomas@monjalon.net \
    /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.