DPDK patches and discussions
 help / color / mirror / Atom feed
From: Gagandeep Singh <G.Singh@nxp.com>
To: Thomas Monjalon <thomas@monjalon.net>,
	Pankaj Chauhan <pankaj.chauhan@nxp.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 2/2] net/enetc: fix big endian build
Date: Wed, 10 Apr 2019 11:27:41 +0000	[thread overview]
Message-ID: <VE1PR04MB636506EE64618853FE8ADF70E12E0@VE1PR04MB6365.eurprd04.prod.outlook.com> (raw)
Message-ID: <20190410112741.fkSgzvJq9E-yRpEf3cyxToPF74s_X1UvuAXAKp8bUWY@z> (raw)



> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Wednesday, April 10, 2019 1:37 AM
> To: Gagandeep Singh <G.Singh@nxp.com>; Pankaj Chauhan
> <pankaj.chauhan@nxp.com>
> Cc: dev@dpdk.org; stable@dpdk.org
> Subject: [EXT] [PATCH v2 2/2] net/enetc: fix big endian build
> 
> WARNING: This email was created outside of NXP. DO NOT CLICK links or
> attachments unless you recognize the sender and know the content is safe.
> 
> 
> 
> Compilation was failing when using a big endian toolchain:
> 
> drivers/net/enetc/enetc_rxtx.c:92:21: error:
>         passing argument 1 of 'rte_constant_bswap64'
>         makes integer from pointer without a cast
> 
> Fixes: 469c6111a799 ("net/enetc: enable Rx and Tx")
> Cc: g.singh@nxp.com
> Cc: stable@dpdk.org
> 
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
>  drivers/net/enetc/enetc_rxtx.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/net/enetc/enetc_rxtx.c b/drivers/net/enetc/enetc_rxtx.c
> index 631e2430d..ef0d7919f 100644
> --- a/drivers/net/enetc/enetc_rxtx.c
> +++ b/drivers/net/enetc/enetc_rxtx.c
> @@ -88,8 +88,9 @@ enetc_refill_rx_ring(struct enetc_bdr *rx_ring, const int
> buff_cnt)
>         rx_swbd = &rx_ring->q_swbd[i];
>         rxbd = ENETC_RXBD(*rx_ring, i);
>         for (j = 0; j < buff_cnt; j++) {
> -               rx_swbd->buffer_addr =
> -                       rte_cpu_to_le_64(rte_mbuf_raw_alloc(rx_ring->mb_pool));
> +               rx_swbd->buffer_addr = (void *)(uintptr_t)
> +                       rte_cpu_to_le_64((uint64_t)(uintptr_t)
> +                                       rte_mbuf_raw_alloc(rx_ring->mb_pool));
>                 rxbd->w.addr = (uint64_t)(uintptr_t)
>                                rx_swbd->buffer_addr->buf_addr +
>                                rx_swbd->buffer_addr->data_off;
> --
> 2.21.0

Hi Thomas,

I have sent a patch-set for ENETC driver having some changes in "enetc_refill_rx_ring".
Is it ok for you if I can merge your changes with my patch-set and push them in v2?

https://patches.dpdk.org/project/dpdk/list/?series=4173 

Thanks,
Gagan


             reply	other threads:[~2019-04-10 11:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-10 11:27 Gagandeep Singh [this message]
2019-04-10 11:27 ` Gagandeep Singh
2019-04-10 11:43 ` Thomas Monjalon
2019-04-10 11:43   ` Thomas Monjalon
  -- strict thread matches above, loose matches on Subject: below --
2019-04-09 19:49 [dpdk-dev] [PATCH 0/2] " Thomas Monjalon
2019-04-09 20:06 ` [dpdk-dev] [PATCH v2 " Thomas Monjalon
2019-04-09 20:06   ` [dpdk-dev] [PATCH v2 2/2] net/enetc: " Thomas Monjalon
2019-04-09 20:06     ` Thomas Monjalon

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=VE1PR04MB636506EE64618853FE8ADF70E12E0@VE1PR04MB6365.eurprd04.prod.outlook.com \
    --to=g.singh@nxp.com \
    --cc=dev@dpdk.org \
    --cc=pankaj.chauhan@nxp.com \
    --cc=stable@dpdk.org \
    --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 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).