DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: jerinj@marvell.com, Amit Gupta <agupta3@marvell.com>
Cc: dev@dpdk.org, ferruh.yigit@intel.com
Subject: Re: [dpdk-dev] [PATCH] drivers: fix ICC compilation issue with i686 for octeontx2
Date: Thu, 04 Jul 2019 16:46:12 +0200	[thread overview]
Message-ID: <2262330.GSOO5BOVcv@xps> (raw)
In-Reply-To: <20190701180346.42906-1-jerinj@marvell.com>

01/07/2019 20:03, jerinj@marvell.com:
> From: Amit Gupta <agupta3@marvell.com>
> 
> Fix the following ICC specific compilation issue with i686 build.
> 
> dpdk/drivers/common/octeontx2/otx2_mbox.c(47): error #2259:
> non-pointer conversion from "unsigned long long" to "struct mbox_hdr *"
> may lose significant bits
> (struct mbox_hdr *)((uintptr_t)mdev->mbase + mbox->tx_start);
> 
> Fixes: 732377a6792e ("mempool/octeontx2: add build infra and device probe")
> Fixes: 371d3212cbed ("common/octeontx2: add build infrastructure and HW definition")
> 
> Signed-off-by: Amit Gupta <agupta3@marvell.com>

Applied, thanks




      reply	other threads:[~2019-07-04 14:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-01 18:03 jerinj
2019-07-04 14:46 ` Thomas Monjalon [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=2262330.GSOO5BOVcv@xps \
    --to=thomas@monjalon.net \
    --cc=agupta3@marvell.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jerinj@marvell.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).