netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: leon@kernel.org
Cc: dledford@redhat.com, jgg@mellanox.com, edwards@mellanox.com,
	linux-rdma@vger.kernel.org, yishaih@mellanox.com,
	saeedm@mellanox.com, netdev@vger.kernel.org, leonro@mellanox.com
Subject: Re: [PATCH mlx5-next] net/mlx5: Fix modify_cq_in alignment
Date: Tue, 23 Jul 2019 11:28:50 -0700 (PDT)	[thread overview]
Message-ID: <20190723.112850.610952032088764951.davem@davemloft.net> (raw)
In-Reply-To: <20190723071255.6588-1-leon@kernel.org>

From: Leon Romanovsky <leon@kernel.org>
Date: Tue, 23 Jul 2019 10:12:55 +0300

> From: Edward Srouji <edwards@mellanox.com>
> 
> Fix modify_cq_in alignment to match the device specification.
> After this fix the 'cq_umem_valid' field will be in the right offset.
> 
> Cc: <stable@vger.kernel.org> # 4.19
> Fixes: bd37197554eb ("net/mlx5: Update mlx5_ifc with DEVX UID bits")
> Signed-off-by: Edward Srouji <edwards@mellanox.com>
> Reviewed-by: Yishai Hadas <yishaih@mellanox.com>
> Signed-off-by: Leon Romanovsky <leonro@mellanox.com>

Very confusing submission on many levels.

Coming from a Mellanox developer using a kernel.org email address.

Targetting the mlx5-next tree, yet CC:'ing stable.

A networking change, for which stable submissions are handled by me by
hand and not via CC:'ing stable.

  reply	other threads:[~2019-07-23 18:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-23  7:12 [PATCH mlx5-next] net/mlx5: Fix modify_cq_in alignment Leon Romanovsky
2019-07-23 18:28 ` David Miller [this message]
2019-07-23 19:04   ` Leon Romanovsky
2019-07-23 20:02     ` David Miller
2019-07-23 20:34       ` Saeed Mahameed
2019-07-24  4:26         ` Leon Romanovsky
2019-07-23 20:25     ` Saeed Mahameed
2019-07-24 20:56     ` Saeed Mahameed
2019-07-25  3:02       ` 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=20190723.112850.610952032088764951.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=dledford@redhat.com \
    --cc=edwards@mellanox.com \
    --cc=jgg@mellanox.com \
    --cc=leon@kernel.org \
    --cc=leonro@mellanox.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=saeedm@mellanox.com \
    --cc=yishaih@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;
as well as URLs for NNTP newsgroup(s).