patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Xu, Rosen" <rosen.xu@intel.com>
To: "Marchand, David" <david.marchand@redhat.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH] bus/ifpga: fix driver header dependency
Date: Tue, 24 Oct 2023 00:23:40 +0000	[thread overview]
Message-ID: <DM6PR11MB425283260888524F63E788F389DFA@DM6PR11MB4252.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20231023144617.1033100-1-david.marchand@redhat.com>

Hi,

> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Monday, October 23, 2023 10:46 PM
> To: dev@dpdk.org
> Cc: stable@dpdk.org; Xu, Rosen <rosen.xu@intel.com>
> Subject: [PATCH] bus/ifpga: fix driver header dependency
> 
> The driver header bus_ifpga_driver.h was not self sufficient.
> Fix this by including dev_driver.h.
> 
> Fixes: 925c074e377b ("bus/ifpga: make driver-only headers private")
> Cc: stable@dpdk.org
> 
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
>  drivers/bus/ifpga/bus_ifpga_driver.h | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/bus/ifpga/bus_ifpga_driver.h
> b/drivers/bus/ifpga/bus_ifpga_driver.h
> index 7b75c2ddbc..5bbe36d6e0 100644
> --- a/drivers/bus/ifpga/bus_ifpga_driver.h
> +++ b/drivers/bus/ifpga/bus_ifpga_driver.h
> @@ -16,6 +16,7 @@ extern "C" {
>  #endif /* __cplusplus */
> 
>  #include <rte_compat.h>
> +#include <dev_driver.h>
>  #include <rte_pci.h>
>  #include <rte_interrupts.h>
>  #include <rte_spinlock.h>
> --
> 2.41.0

Acked-by: Rosen Xu <rosen.xu@intel.com>

  parent reply	other threads:[~2023-10-24  0:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-23 14:46 David Marchand
2023-10-23 15:05 ` Bruce Richardson
2023-10-24  0:23 ` Xu, Rosen [this message]
2023-10-26  8:41   ` David Marchand

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=DM6PR11MB425283260888524F63E788F389DFA@DM6PR11MB4252.namprd11.prod.outlook.com \
    --to=rosen.xu@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --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).