From: "Xu, Rosen" <rosen.xu@intel.com>
To: "Marchand, David" <david.marchand@redhat.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Tianfei Zhang <tianfei.zhang@intel.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>
Subject: RE: [PATCH] bus/ifpga: remove dead code
Date: Tue, 19 Dec 2023 01:18:10 +0000 [thread overview]
Message-ID: <DM6PR11MB4252493E36DA6174B9042CF38997A@DM6PR11MB4252.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20231218154527.1507785-1-david.marchand@redhat.com>
Hi
> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Monday, December 18, 2023 11:45 PM
> To: dev@dpdk.org
> Cc: Xu, Rosen <rosen.xu@intel.com>; Tianfei Zhang
> <tianfei.zhang@intel.com>; Zhang, Qi Z <qi.z.zhang@intel.com>
> Subject: [PATCH] bus/ifpga: remove dead code
>
> This macro was never used.
>
> Fixes: 05fa3d4a6539 ("bus/ifpga: add Intel FPGA bus library")
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
> drivers/bus/ifpga/ifpga_logs.h | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/drivers/bus/ifpga/ifpga_logs.h b/drivers/bus/ifpga/ifpga_logs.h
> index 873e0a4f2f..248bccba5d 100644
> --- a/drivers/bus/ifpga/ifpga_logs.h
> +++ b/drivers/bus/ifpga/ifpga_logs.h
> @@ -9,10 +9,6 @@
>
> extern int ifpga_bus_logtype;
>
> -#define IFPGA_LOG(level, fmt, args...) \
> - rte_log(RTE_LOG_ ## level, ifpga_bus_logtype, "%s(): " fmt "\n", \
> - __func__, ##args)
> -
> #define IFPGA_BUS_LOG(level, fmt, args...) \
> rte_log(RTE_LOG_ ## level, ifpga_bus_logtype, "%s(): " fmt "\n", \
> __func__, ##args)
> --
> 2.43.0
Acked-by: Rosen Xu <rosen.xu@intel.com>
next prev parent reply other threads:[~2023-12-19 1:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 15:45 David Marchand
2023-12-18 15:47 ` Bruce Richardson
2023-12-19 1:18 ` Xu, Rosen [this message]
2024-01-19 11:08 ` 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=DM6PR11MB4252493E36DA6174B9042CF38997A@DM6PR11MB4252.namprd11.prod.outlook.com \
--to=rosen.xu@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.com \
--cc=tianfei.zhang@intel.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).