From: "Walsh, Conor" <conor.walsh@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Richardson, Bruce" <bruce.richardson@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>,
"Chengwen Feng" <fengchengwen@huawei.com>,
"Laatz, Kevin" <kevin.laatz@intel.com>,
"Morten Brørup" <mb@smartsharesystems.com>
Subject: RE: [PATCH] dmadev: add missing header include
Date: Tue, 22 Feb 2022 13:44:04 +0000 [thread overview]
Message-ID: <PH0PR11MB52078058A9D31757F21BD883FF3B9@PH0PR11MB5207.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220222114104.463353-1-thomas@monjalon.net>
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Tuesday 22 February 2022 11:41
> To: dev@dpdk.org
> Cc: Richardson, Bruce <bruce.richardson@intel.com>; stable@dpdk.org;
> Chengwen Feng <fengchengwen@huawei.com>; Laatz, Kevin
> <kevin.laatz@intel.com>; Morten Brørup <mb@smartsharesystems.com>;
> Walsh, Conor <conor.walsh@intel.com>
> Subject: [PATCH] dmadev: add missing header include
>
> When checking C++ compatibility of SDK headers,
> an error is detected by the compiler:
>
> lib/dmadev/rte_dmadev_pmd.h:95:23: error:
> ‘RTE_DEV_NAME_MAX_LEN’ undeclared here (not in a function)
>
> The header file rte_dev.h must be included.
>
> Fixes: b36970f2e13e ("dmadev: introduce DMA device library")
> Cc: stable@dpdk.org
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
Acked-by: Conor Walsh <conor.walsh@intel.com>
prev parent reply other threads:[~2022-02-22 13:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 11:41 Thomas Monjalon
2022-02-22 11:48 ` Bruce Richardson
2022-02-22 13:44 ` Thomas Monjalon
2022-02-22 13:44 ` Walsh, Conor [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=PH0PR11MB52078058A9D31757F21BD883FF3B9@PH0PR11MB5207.namprd11.prod.outlook.com \
--to=conor.walsh@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=kevin.laatz@intel.com \
--cc=mb@smartsharesystems.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).