linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhu Yanjun <yanjun.zhu@linux.dev>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Doug Ledford <dledford@redhat.com>,
	Jason Gunthorpe <jgg@mellanox.com>
Cc: Junxian Huang <huangjunxian6@hisilicon.com>,
	Leon Romanovsky <leon@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Yuyu Li <liyuyu6@huawei.com>
Subject: Re: linux-next: manual merge of the rdma tree with Linus' tree
Date: Mon, 6 Jan 2025 15:16:50 +0100	[thread overview]
Message-ID: <c2e792ef-054e-4dfd-a966-f975d3b92ab6@linux.dev> (raw)
In-Reply-To: <20250106120252.000a2afa@canb.auug.org.au>


On 06.01.25 02:02, Stephen Rothwell wrote:
> Hi all,
>
> On Mon, 6 Jan 2025 10:51:06 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>> Today's linux-next merge of the rdma tree got a conflict in:
>>
>>    drivers/infiniband/sw/rxe/rxe_net.c
>>
>> between commit:
>>
>>    2ac5415022d1 ("RDMA/rxe: Remove the direct link to net_device")
>>
>> from Linus' tree and commit:
>>
>>    958152336cfa ("RDMA/rxe: Remove deliver net device event")
>>
>> 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.
>>
>> -- 
>> Cheers,
>> Stephen Rothwell
>>
>> diff --cc drivers/infiniband/sw/rxe/rxe_net.c
>> index 8cc64ceeb356,d400aaab0e70..000000000000
>> --- a/drivers/infiniband/sw/rxe/rxe_net.c
>> +++ b/drivers/infiniband/sw/rxe/rxe_net.c
>> @@@ -595,13 -577,7 +585,13 @@@ void rxe_port_down(struct rxe_dev *rxe
>>    
>>    void rxe_set_port_state(struct rxe_dev *rxe)
>>    {
>>   -	if (ib_get_curr_port_state(rxe->ndev) == IB_PORT_ACTIVE)
>>   +	struct net_device *ndev;
>>   +
>>   +	ndev = rxe_ib_device_get_netdev(&rxe->ib_dev);
>>   +	if (!ndev)
>>   +		return;
>>   +
>> - 	if (netif_running(ndev) && netif_carrier_ok(ndev))
>> ++	if (ib_get_curr_port_state(ndev) == IB_PORT_ACTIVE)
>>    		rxe_port_up(rxe);
>>    	else
>>    		rxe_port_down(rxe);
> It also needed the following merge fix patch:
>
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Mon, 6 Jan 2025 11:36:03 +1100
> Subject: [PATCH] fix up for "RDMA/rxe: Remove deliver net device event"
>
> interacting with "RDMA/rxe: Remove the direct link to net_device"
>
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> ---
>   drivers/infiniband/sw/rxe/rxe_verbs.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/infiniband/sw/rxe/rxe_verbs.c b/drivers/infiniband/sw/rxe/rxe_verbs.c
> index 47d57046fad4..6152a0fdfc8c 100644
> --- a/drivers/infiniband/sw/rxe/rxe_verbs.c
> +++ b/drivers/infiniband/sw/rxe/rxe_verbs.c
> @@ -62,7 +62,7 @@ static int rxe_query_port(struct ib_device *ibdev,
>   	ret = ib_get_eth_speed(ibdev, port_num, &attr->active_speed,
>   			       &attr->active_width);
>   
> -	attr->state = ib_get_curr_port_state(rxe->ndev);
> +	attr->state = ib_get_curr_port_state(ndev);
>   	if (attr->state == IB_PORT_ACTIVE)
>   		attr->phys_state = IB_PORT_PHYS_STATE_LINK_UP;
>   	else if (dev_get_flags(ndev) & IFF_UP)

To the above 2 changes, I am fine with them. The changes are from the 
following commit.

When I worked on the commit 2ac5415022d1 ("RDMA/rxe: Remove the direct 
link to net_device"),

the commit 958152336cfa ("RDMA/rxe: Remove deliver net device event") is 
not merged into linux upstream.

commit 958152336cfafdec1f42d3d44253805282dc1321
Author: Yuyu Li <liyuyu6@huawei.com>
Date:   Fri Nov 22 18:53:02 2024 +0800

     RDMA/rxe: Remove deliver net device event

     Since the netdev events of link status is now handled in ib_core,
     remove the related code in drivers.

     In addition, remove the setting of port->attr.state in rxe_port_up()
     and rxe_port_down(), as it is only used in rxe_query_port(), and it
     can be replaced by ib_get_curr_port_state().

     Signed-off-by: Yuyu Li <liyuyu6@huawei.com>
     Signed-off-by: Junxian Huang <huangjunxian6@hisilicon.com>
     Signed-off-by: Leon Romanovsky <leon@kernel.org>

Thanks a lot.

Zhu Yanjun

-- 
Best Regards,
Yanjun.Zhu


  reply	other threads:[~2025-01-06 14:17 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-05 23:51 linux-next: manual merge of the rdma tree with Linus' tree Stephen Rothwell
2025-01-06  1:02 ` Stephen Rothwell
2025-01-06 14:16   ` Zhu Yanjun [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-09-11  2:23 Stephen Rothwell
2025-09-11 11:03 ` Leon Romanovsky
2025-05-14  2:24 Stephen Rothwell
2025-05-14  8:17 ` Leon Romanovsky
2025-04-22  4:30 Stephen Rothwell
2025-03-20  1:08 Stephen Rothwell
2025-03-20  6:35 ` Leon Romanovsky
2025-01-06  0:13 Stephen Rothwell
2025-01-14 20:48 ` Jason Gunthorpe
2025-01-14 21:27   ` Stephen Rothwell
2025-01-15  0:41     ` Jason Gunthorpe
2025-01-15  1:07       ` Stephen Rothwell
2025-01-15 11:17         ` Bernard Metzler
2023-06-22  1:52 Stephen Rothwell
2021-05-21  0:34 Stephen Rothwell
2021-04-15  2:05 Stephen Rothwell
2021-02-10  2:15 Stephen Rothwell
2021-02-10 18:57 ` Pearson, Robert B
2021-02-10 20:36   ` Jason Gunthorpe
2021-02-10 22:08     ` Pearson, Robert B
2021-02-11 20:03       ` Martin Wilck
2019-11-05  1:17 Stephen Rothwell
2019-11-05  2:21 ` Jason Gunthorpe
2019-11-05  2:28   ` Stephen Rothwell
2019-10-24  0:01 Stephen Rothwell
2019-10-28 19:30 ` Jason Gunthorpe
2019-06-20  2:10 Stephen Rothwell
2019-06-20  3:25 ` Doug Ledford
2019-06-20  2:06 Stephen Rothwell
2019-06-20  3:24 ` Doug Ledford
2019-06-14  3:00 Stephen Rothwell
2019-06-14 13:11 ` Doug Ledford
2018-09-28  0:01 Stephen Rothwell
2018-09-29  2:57 ` Parav Pandit
2018-08-06  2:01 Stephen Rothwell
2018-08-06 19:41 ` Jason Gunthorpe
2018-08-06 21:49   ` Stephen Rothwell
2017-08-08  2:11 Stephen Rothwell
2017-07-14  1:14 Stephen Rothwell
2017-07-14  1:17 ` Doug Ledford
2017-07-14  3:34   ` Leon Romanovsky
2017-07-14  3:50     ` Stephen Rothwell
2017-07-14  4:55       ` Leon Romanovsky
2017-07-14 12:03         ` Doug Ledford
2017-07-14 13:46           ` Leon Romanovsky
2017-07-14  4:12     ` Doug Ledford
2017-07-14  4:54       ` Leon Romanovsky
2017-07-14 14:33         ` Doug Ledford
2017-07-14 15:10           ` Leon Romanovsky
2016-12-15  0:47 Stephen Rothwell
2016-10-10  0:59 Stephen Rothwell
2016-10-10  0:54 Stephen Rothwell
2016-08-05  1:05 Stephen Rothwell
2016-08-05  1:01 Stephen Rothwell
2016-08-05  0:52 Stephen Rothwell
2016-05-19  1:45 Stephen Rothwell
2016-03-22  0:33 Stephen Rothwell
2016-03-22  0:29 Stephen Rothwell
2016-03-22  0:24 Stephen Rothwell
2016-03-22  0:17 Stephen Rothwell
2015-11-01  7:48 Stephen Rothwell
2015-11-02 10:40 ` Sagi Grimberg

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=c2e792ef-054e-4dfd-a966-f975d3b92ab6@linux.dev \
    --to=yanjun.zhu@linux.dev \
    --cc=dledford@redhat.com \
    --cc=huangjunxian6@hisilicon.com \
    --cc=jgg@mellanox.com \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=liyuyu6@huawei.com \
    --cc=sfr@canb.auug.org.au \
    /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).