linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Saeed Mahameed <saeedm@mellanox.com>
To: "yamada.masahiro@socionext.com" <yamada.masahiro@socionext.com>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"leon@kernel.org" <leon@kernel.org>
Subject: Re: [PATCH] net/mlx5e: remove meaningless CFLAGS_tracepoint.o
Date: Fri, 19 Apr 2019 23:16:31 +0000	[thread overview]
Message-ID: <d938a56a3350fba18bd23f43efb582835c90c94d.camel@mellanox.com> (raw)
In-Reply-To: <20190419051731.15111-1-yamada.masahiro@socionext.com>

On Fri, 2019-04-19 at 14:17 +0900, Masahiro Yamada wrote:
> CFLAGS_tracepoint.o specifies CFLAGS for compiling tracepoint.c but
> it does not exist under drivers/net/ethernet/mellanox/mlx5/core/.
> 
> CFLAGS_tracepoint.o is unused.
> 
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> ---
> 
>  drivers/net/ethernet/mellanox/mlx5/core/Makefile | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/drivers/net/ethernet/mellanox/mlx5/core/Makefile
> b/drivers/net/ethernet/mellanox/mlx5/core/Makefile
> index 1a16f6d73cbc..fa12c2ca9fc5 100644
> --- a/drivers/net/ethernet/mellanox/mlx5/core/Makefile
> +++ b/drivers/net/ethernet/mellanox/mlx5/core/Makefile
> @@ -57,5 +57,3 @@ mlx5_core-$(CONFIG_MLX5_EN_IPSEC) +=
> en_accel/ipsec.o en_accel/ipsec_rxtx.o \
>  				     en_accel/ipsec_stats.o
>  
>  mlx5_core-$(CONFIG_MLX5_EN_TLS) += en_accel/tls.o
> en_accel/tls_rxtx.o en_accel/tls_stats.o
> -
> -CFLAGS_tracepoint.o := -I$(src)

LGTM, applied to mlx5 branch, will be sent upstream shortly.

Thanks,
Saeed.

      reply	other threads:[~2019-04-19 23:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-19  5:17 [PATCH] net/mlx5e: remove meaningless CFLAGS_tracepoint.o Masahiro Yamada
2019-04-19 23:16 ` Saeed Mahameed [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=d938a56a3350fba18bd23f43efb582835c90c94d.camel@mellanox.com \
    --to=saeedm@mellanox.com \
    --cc=davem@davemloft.net \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=yamada.masahiro@socionext.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).