linux-kernel - Re: linux-next: manual merge of the driver-core tree with the rdma tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <2025061939-blurt-stereo-0f01@gregkh>
Date: Thu, 19 Jun 2025 10:18:45 +0200
From: Greg KH <greg@...ah.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Dennis Dalessandro <dennis.dalessandro@...nelisnetworks.com>,
	Jason Gunthorpe <jgg@...dia.com>, Jason Gunthorpe <jgg@...pe.ca>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Next Mailing List <linux-next@...r.kernel.org>,
	Thomas Weißschuh <linux@...ssschuh.net>
Subject: Re: linux-next: manual merge of the driver-core tree with the rdma
 tree

On Thu, Jun 19, 2025 at 04:30:41PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> Today's linux-next merge of the driver-core tree got a conflict in:
> 
>   drivers/infiniband/hw/qib/qib_sysfs.c
> 
> between commit:
> 
>   24baad32b710 ("RDMA/qib: Remove outdated driver")
> 
> from the rdma tree and commit:
> 
>   fb506e31b3d5 ("sysfs: treewide: switch back to attribute_group::bin_attrs")
> 
> from the driver-core tree.
> 
> I fixed it up (I just removed the file) 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.
> 

Looks good, thanks!

greg k-h