patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: luca.boccassi@gmail.com
Cc: stable@dpdk.org, ktraynor@redhat.com, Luca Boccassi <bluca@debian.org>
Subject: Re: [PATCH 20.11 2/2] dpaa2: fix build with RTE_LIBRTE_IEEE1588
Date: Tue, 29 Mar 2022 16:20:50 +0200	[thread overview]
Message-ID: <CAATJJ0KoL60RTyFd_LWpw2QRfdGjeP+bv289OtVzKQz44n1Tfg@mail.gmail.com> (raw)
In-Reply-To: <20220329120953.152396-2-luca.boccassi@gmail.com>

On Tue, Mar 29, 2022 at 2:10 PM <luca.boccassi@gmail.com> wrote:
>
> From: Luca Boccassi <bluca@debian.org>
>
> ../drivers/net/dpaa2/dpaa2_rxtx.c: In function ‘dpaa2_dev_rx’:
> ../drivers/net/dpaa2/dpaa2_rxtx.c:863:4: error: ‘priv’ undeclared (first use in this function); did you mean ‘ldiv’?
>     priv->rx_timestamp =
>     ^~~~
>     ldiv
>
> Bugzilla ID: 982
>
> Fixes: 1d10966a22ca ("net/dpaa2: fix timestamping for IEEE1588")
>
> Signed-off-by: Luca Boccassi <bluca@debian.org>

It was unclear at first why it needs the if defined, thanks for the
IRC discussion.
While not nice I think it makes sense as a build-fix.
+1, but since I'm not a subject matter expert I'm holding back an
official signed-off for this.

> ---
>  drivers/net/dpaa2/dpaa2_rxtx.c | 3 +++
>  1 file changed, 3 insertions(+)
>
> diff --git a/drivers/net/dpaa2/dpaa2_rxtx.c b/drivers/net/dpaa2/dpaa2_rxtx.c
> index ecd004f9fa..23e193f86c 100644
> --- a/drivers/net/dpaa2/dpaa2_rxtx.c
> +++ b/drivers/net/dpaa2/dpaa2_rxtx.c
> @@ -772,6 +772,9 @@ dpaa2_dev_rx(void *queue, struct rte_mbuf **bufs, uint16_t nb_pkts)
>         const struct qbman_fd *fd;
>         struct qbman_pull_desc pulldesc;
>         struct rte_eth_dev_data *eth_data = dpaa2_q->eth_data;
> +#if defined(RTE_LIBRTE_IEEE1588)
> +       struct dpaa2_dev_priv *priv = eth_data->dev_private;
> +#endif
>
>         if (unlikely(!DPAA2_PER_LCORE_DPIO)) {
>                 ret = dpaa2_affine_qbman_swp();
> --
> 2.34.1
>


-- 
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd

  parent reply	other threads:[~2022-03-29 14:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29 12:09 [PATCH 20.11 1/2] Revert "regexdev: fix section attribute of symbols" luca.boccassi
2022-03-29 12:09 ` [PATCH 20.11 2/2] dpaa2: fix build with RTE_LIBRTE_IEEE1588 luca.boccassi
2022-03-29 14:11   ` Luca Boccassi
2022-03-31 12:25     ` Luca Boccassi
2022-04-01  5:29       ` [EXT] " Vanshika Shukla
2022-04-01  7:19         ` Christian Ehrhardt
2022-03-31 15:19     ` Hemant Agrawal
2022-03-29 14:20   ` Christian Ehrhardt [this message]
2022-03-29 14:07 ` [PATCH 20.11 1/2] Revert "regexdev: fix section attribute of symbols" Christian Ehrhardt

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=CAATJJ0KoL60RTyFd_LWpw2QRfdGjeP+bv289OtVzKQz44n1Tfg@mail.gmail.com \
    --to=christian.ehrhardt@canonical.com \
    --cc=bluca@debian.org \
    --cc=ktraynor@redhat.com \
    --cc=luca.boccassi@gmail.com \
    --cc=stable@dpdk.org \
    /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).