public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@mellanox.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Doug Ledford <dledford@redhat.com>,
	Leon Romanovsky <leonro@mellanox.com>,
	RDMA mailing list <linux-rdma@vger.kernel.org>,
	Saeed Mahameed <saeedm@mellanox.com>,
	linux-netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH mlx5-next] RDMA/mad: Reduce MAD scope to mlx5_ib only
Date: Mon, 14 Jan 2019 19:56:23 +0000	[thread overview]
Message-ID: <20190114195615.GV22875@mellanox.com> (raw)
In-Reply-To: <20190113135704.10032-1-leon@kernel.org>

On Sun, Jan 13, 2019 at 03:57:04PM +0200, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@mellanox.com>
> 
> Management Datagram Interface (MAD) is applicable
> only when physical port is Infiniband. It makes MAD
> command logic to be completely unrelated to eth/core
> parts of mlx5.
 
> Signed-off-by: Leon Romanovsky <leonro@mellanox.com>
> ---
>  drivers/infiniband/hw/mlx5/cmd.c              | 37 +++++++++
>  drivers/infiniband/hw/mlx5/cmd.h              |  2 +
>  drivers/infiniband/hw/mlx5/mad.c              | 11 ++-
>  drivers/infiniband/hw/mlx5/mlx5_ib.h          |  3 -
>  .../net/ethernet/mellanox/mlx5/core/Makefile  |  2 +-
>  drivers/net/ethernet/mellanox/mlx5/core/mad.c | 75 -------------------
>  include/linux/mlx5/driver.h                   |  2 -
>  7 files changed, 47 insertions(+), 85 deletions(-)
>  delete mode 100644 drivers/net/ethernet/mellanox/mlx5/core/mad.c

Acked-by: Jason Gunthorpe <jgg@mellanox.com>

Jason

  reply	other threads:[~2019-01-14 19:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-13 13:57 [PATCH mlx5-next] RDMA/mad: Reduce MAD scope to mlx5_ib only Leon Romanovsky
2019-01-14 19:56 ` Jason Gunthorpe [this message]
2019-01-15  8:05   ` Leon Romanovsky

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=20190114195615.GV22875@mellanox.com \
    --to=jgg@mellanox.com \
    --cc=dledford@redhat.com \
    --cc=leon@kernel.org \
    --cc=leonro@mellanox.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=saeedm@mellanox.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