From: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
To: Jakub Kicinski <kuba@kernel.org>, dledford@redhat.com, jgg@nvidia.com
Cc: linux-rdma@vger.kernel.org,
mike.marciniszyn@cornelisnetworks.com, jgg@ziepe.ca,
liangwenpeng@huawei.com, liweihang@huawei.com,
mustafa.ismail@intel.com, shiraz.saleem@intel.com,
benve@cisco.com, neescoba@cisco.com
Subject: Re: [PATCH rdma-next 3/3] RDMA: constify netdev->dev_addr accesses
Date: Thu, 21 Oct 2021 07:48:38 -0400 [thread overview]
Message-ID: <9e112f59-e980-a892-343d-9e21924b6f93@cornelisnetworks.com> (raw)
In-Reply-To: <20211019182604.1441387-4-kuba@kernel.org>
On 10/19/21 2:26 PM, Jakub Kicinski wrote:
> netdev->dev_addr will become const soon, make sure
> drivers propagate the qualifier.
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> CC: mike.marciniszyn@cornelisnetworks.com
> CC: dennis.dalessandro@cornelisnetworks.com
> CC: dledford@redhat.com
> CC: jgg@ziepe.ca
> CC: liangwenpeng@huawei.com
> CC: liweihang@huawei.com
> CC: mustafa.ismail@intel.com
> CC: shiraz.saleem@intel.com
> CC: benve@cisco.com
> CC: neescoba@cisco.com
> CC: linux-rdma@vger.kernel.org
> ---
> drivers/infiniband/hw/bnxt_re/qplib_res.c | 2 +-
> drivers/infiniband/hw/bnxt_re/qplib_res.h | 2 +-
> drivers/infiniband/hw/bnxt_re/qplib_sp.c | 6 +++---
> drivers/infiniband/hw/bnxt_re/qplib_sp.h | 5 +++--
> drivers/infiniband/hw/hfi1/ipoib_main.c | 2 +-
> drivers/infiniband/hw/hns/hns_roce_device.h | 3 ++-
> drivers/infiniband/hw/hns/hns_roce_hw_v1.c | 10 +++++-----
> drivers/infiniband/hw/hns/hns_roce_hw_v2.c | 6 +++---
> drivers/infiniband/hw/hns/hns_roce_main.c | 3 ++-
> drivers/infiniband/hw/irdma/cm.h | 4 ++--
> drivers/infiniband/hw/irdma/hw.c | 7 ++++---
> drivers/infiniband/hw/irdma/main.h | 5 +++--
> drivers/infiniband/hw/irdma/trace_cm.h | 8 +++++---
> drivers/infiniband/hw/irdma/utils.c | 4 ++--
> drivers/infiniband/hw/irdma/verbs.c | 2 +-
> drivers/infiniband/hw/usnic/usnic_fwd.c | 2 +-
> drivers/infiniband/hw/usnic/usnic_fwd.h | 2 +-
> 17 files changed, 40 insertions(+), 33 deletions(-)
For hfi1:
Acked-by: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
next prev parent reply other threads:[~2021-10-21 11:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 18:26 [PATCH rdma-next 0/3] rdma: prepare for const netdev->dev_addr Jakub Kicinski
2021-10-19 18:26 ` [PATCH rdma-next 1/3] ipoib: use dev_addr_mod() Jakub Kicinski
2021-10-21 9:51 ` Leon Romanovsky
2021-10-19 18:26 ` [PATCH rdma-next 2/3] mlx5: " Jakub Kicinski
2021-10-21 9:49 ` Leon Romanovsky
2021-10-21 12:58 ` Jakub Kicinski
2021-10-21 13:40 ` Leon Romanovsky
2021-10-21 13:40 ` Leon Romanovsky
2021-10-19 18:26 ` [PATCH rdma-next 3/3] RDMA: constify netdev->dev_addr accesses Jakub Kicinski
2021-10-21 9:51 ` Leon Romanovsky
2021-10-21 11:48 ` Dennis Dalessandro [this message]
2021-10-25 17:36 ` [PATCH rdma-next 0/3] rdma: prepare for const netdev->dev_addr Jason Gunthorpe
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=9e112f59-e980-a892-343d-9e21924b6f93@cornelisnetworks.com \
--to=dennis.dalessandro@cornelisnetworks.com \
--cc=benve@cisco.com \
--cc=dledford@redhat.com \
--cc=jgg@nvidia.com \
--cc=jgg@ziepe.ca \
--cc=kuba@kernel.org \
--cc=liangwenpeng@huawei.com \
--cc=linux-rdma@vger.kernel.org \
--cc=liweihang@huawei.com \
--cc=mike.marciniszyn@cornelisnetworks.com \
--cc=mustafa.ismail@intel.com \
--cc=neescoba@cisco.com \
--cc=shiraz.saleem@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).