Linux-Next discussions
 help / color / mirror / Atom feed
From: broonie@kernel.org
To: Doug Ledford <dledford@redhat.com>, Jason Gunthorpe <jgg@mellanox.com>
Cc: Haoyue Xu <xuhaoyue1@hisilicon.com>,
	Jason Gunthorpe <jgg@nvidia.com>, Jason Gunthorpe <jgg@ziepe.ca>,
	Leon Romanovsky <leon@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: manual merge of the rdma tree with the origin tree
Date: Thu, 29 Sep 2022 13:40:05 +0100	[thread overview]
Message-ID: <20220929124005.105149-1-broonie@kernel.org> (raw)

Hi all,

Today's linux-next merge of the rdma tree got conflicts in:

  drivers/infiniband/hw/hns/hns_roce_hw_v2.c
  drivers/infiniband/hw/hns/hns_roce_main.c

between commit:

  45baad7dd98f4 ("RDMA/hns: Remove the num_qpc_timer variable")

from the origin tree and commits:

  29dc063596772 ("RDMA/hns: Remove redundant 'use_lowmem' argument from hns_roce_init_hem_table()")
  5436272c8cf4e ("RDMA/hns: Remove redundant 'num_mtt_segs' and 'max_extend_sg'")

from the rdma tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

diff --cc drivers/infiniband/hw/hns/hns_roce_hw_v2.c
index c780646bd60ac,2d0192057d1af..0000000000000
--- a/drivers/infiniband/hw/hns/hns_roce_hw_v2.c
+++ b/drivers/infiniband/hw/hns/hns_roce_hw_v2.c
@@@ -2272,7 -2270,7 +2270,6 @@@ static int hns_roce_query_pf_caps(struc
  	caps->max_sq_inline	     = le16_to_cpu(resp_a->max_sq_inline);
  	caps->max_rq_sg		     = le16_to_cpu(resp_a->max_rq_sg);
  	caps->max_rq_sg = roundup_pow_of_two(caps->max_rq_sg);
- 	caps->max_extend_sg	     = le32_to_cpu(resp_a->max_extend_sg);
 -	caps->num_qpc_timer	     = le16_to_cpu(resp_a->num_qpc_timer);
  	caps->max_srq_sges	     = le16_to_cpu(resp_a->max_srq_sges);
  	caps->max_srq_sges = roundup_pow_of_two(caps->max_srq_sges);
  	caps->num_aeq_vectors	     = resp_a->num_aeq_vectors;
diff --cc drivers/infiniband/hw/hns/hns_roce_main.c
index 4ccb217b2841d,53c53c20360d1..0000000000000
--- a/drivers/infiniband/hw/hns/hns_roce_main.c
+++ b/drivers/infiniband/hw/hns/hns_roce_main.c
@@@ -725,10 -734,10 +734,10 @@@ static int hns_roce_init_hem(struct hns
  		ret = hns_roce_init_hem_table(hr_dev, &hr_dev->qpc_timer_table,
  					      HEM_TYPE_QPC_TIMER,
  					      hr_dev->caps.qpc_timer_entry_sz,
- 					      hr_dev->caps.qpc_timer_bt_num, 1);
 -					      hr_dev->caps.num_qpc_timer);
++					      hr_dev->caps.qpc_timer_bt_num);
  		if (ret) {
  			dev_err(dev,
- 				"Failed to init QPC timer memory, aborting.\n");
+ 				"failed to init QPC timer memory, aborting.\n");
  			goto err_unmap_ctx;
  		}
  	}

             reply	other threads:[~2022-09-29 12:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-29 12:40 broonie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-01-19 16:25 linux-next: manual merge of the rdma tree with the origin tree Mark Brown
2026-05-18 12:26 Mark Brown

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=20220929124005.105149-1-broonie@kernel.org \
    --to=broonie@kernel.org \
    --cc=dledford@redhat.com \
    --cc=jgg@mellanox.com \
    --cc=jgg@nvidia.com \
    --cc=jgg@ziepe.ca \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=xuhaoyue1@hisilicon.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