public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Greg KH <greg@kroah.com>
Cc: "Dennis Dalessandro" <dennis.dalessandro@cornelisnetworks.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Jason Gunthorpe" <jgg@nvidia.com>,
	"Jason Gunthorpe" <jgg@ziepe.ca>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Linux Next Mailing List" <linux-next@vger.kernel.org>,
	"Thomas Weißschuh" <linux@weissschuh.net>
Subject: Re: linux-next: manual merge of the driver-core tree with the rdma tree
Date: Wed, 30 Jul 2025 09:15:48 +1000	[thread overview]
Message-ID: <20250730091548.0d669f33@canb.auug.org.au> (raw)
In-Reply-To: <20250619163041.7e4f9c96@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 958 bytes --]

Hi all,

On Thu, 19 Jun 2025 16:30:41 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> 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.

This is now a conflict between the rdma tree and Linus' tree.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      parent reply	other threads:[~2025-07-29 23:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-19  6:30 linux-next: manual merge of the driver-core tree with the rdma tree Stephen Rothwell
2025-06-19  8:18 ` Greg KH
2025-07-29 23:15 ` Stephen Rothwell [this message]

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=20250730091548.0d669f33@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=dennis.dalessandro@cornelisnetworks.com \
    --cc=greg@kroah.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jgg@nvidia.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux@weissschuh.net \
    /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