Linux-Next discussions
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
	"Christophe JAILLET" <christophe.jaillet@wanadoo.fr>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Linux Next Mailing List" <linux-next@vger.kernel.org>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: linux-next: manual merge of the driver-core tree with the mm tree
Date: Wed, 24 Jul 2024 08:33:29 +0200	[thread overview]
Message-ID: <2024072446-scooter-maritime-4888@gregkh> (raw)
In-Reply-To: <20240724085721.7fac67d8@canb.auug.org.au>

On Wed, Jul 24, 2024 at 08:57:21AM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> On Wed, 12 Jun 2024 12:36:40 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > 
> > Today's linux-next merge of the driver-core tree got a conflict in:
> > 
> >   drivers/fsi/fsi-occ.c
> > 
> > between commit:
> > 
> >   2d2bf1e680a9 ("fsi: occ: remove usage of the deprecated ida_simple_xx() API")
> > 
> > from the mm-nonmm-unstable branch of the mm tree and commit:
> > 
> >   29f102dbb11f ("fsi: occ: Convert to platform remove callback returning void")
> > 
> > from the driver-core 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/fsi/fsi-occ.c
> > index f7157c1d77d8,21d2666c4195..000000000000
> > --- a/drivers/fsi/fsi-occ.c
> > +++ b/drivers/fsi/fsi-occ.c
> > @@@ -718,9 -719,7 +718,7 @@@ static void occ_remove(struct platform_
> >   	else
> >   		device_for_each_child(&pdev->dev, NULL, occ_unregister_of_child);
> >   
> >  -	ida_simple_remove(&occ_ida, occ->idx);
> >  +	ida_free(&occ_ida, occ->idx);
> > - 
> > - 	return 0;
> >   }
> >   
> >   static const struct of_device_id occ_match[] = {
> 
> This conflict is now between the driver-core tree and Linus tree.

Yeah, there's lots of conflicts now, I was waiting for all of these to
be merged before submitting my pull request.  I'll do some test builds
here locally today before submitting it with links to these resolutions
to give Linus a hint of what to do.

thanks,

greg k-h

      reply	other threads:[~2024-07-24  6:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-12  2:36 linux-next: manual merge of the driver-core tree with the mm tree Stephen Rothwell
2024-06-12  6:07 ` Uwe Kleine-König
2024-07-23 22:57 ` Stephen Rothwell
2024-07-24  6:33   ` Greg KH [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=2024072446-scooter-maritime-4888@gregkh \
    --to=greg@kroah.com \
    --cc=akpm@linux-foundation.org \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=u.kleine-koenig@pengutronix.de \
    /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