All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Cc: "Stephen Rothwell" <sfr@canb.auug.org.au>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Linux Next Mailing List" <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the pci tree with the pci-current tree
Date: Thu, 24 Oct 2024 13:50:07 -0500	[thread overview]
Message-ID: <20241024185007.GA968089@bhelgaas> (raw)
In-Reply-To: <CACMJSesMpF9v76Geob83ONLUQUh7DXRYbPV+JOGNkCN=Fd-phw@mail.gmail.com>

On Thu, Oct 24, 2024 at 08:56:11AM +0200, Bartosz Golaszewski wrote:
> On Thu, 24 Oct 2024 at 02:25, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Hi all,
> >
> > Today's linux-next merge of the pci tree got a conflict in:
> >
> >   drivers/pci/pwrctl/pci-pwrctl-pwrseq.c
> >
> > between commit:
> >
> >   ad783b9f8e78 ("PCI/pwrctl: Abandon QCom WCN probe on pre-pwrseq device-trees")
> >
> > from the pci-current tree and commit:
> >
> >   98cb476c98e9 ("PCI/pwrctl: Use generic device_get_match_data() instead of OF version")
> >
> 
> This can be dropped from pci-current given that the former will get
> upstream into v6.12.

I dropped 98cb476c98e9 from pci/next, thanks!

> > from the pci tree.
> >
> > I fixed it up (the former commit includes the changes from the latter)
> > 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

  reply	other threads:[~2024-10-24 18:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-24  0:25 linux-next: manual merge of the pci tree with the pci-current tree Stephen Rothwell
2024-10-24  6:56 ` Bartosz Golaszewski
2024-10-24 18:50   ` Bjorn Helgaas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-10-09 19:27 Mark Brown
2026-10-13  7:55 ` Geert Uytterhoeven
2026-10-13 11:15   ` Lukas Wunner
2026-01-05  0:55 Stephen Rothwell
2024-06-03  0:24 Stephen Rothwell
2018-08-01  0:42 Stephen Rothwell
2016-02-24  0:02 Stephen Rothwell
2014-03-12 13:00 Mark Brown
2010-03-26  0:57 Stephen Rothwell
2010-03-26  2:10 ` Jesse Barnes
2010-03-26  2:48   ` Stephen Rothwell
2010-03-26 16:03     ` Jesse Barnes
2010-03-26 14:43 ` Bjorn Helgaas
2009-02-06  2:50 Stephen Rothwell
2009-02-06 17:09 ` Jesse Barnes
2009-02-06 23:49   ` Rafael J. Wysocki
2009-02-07  0:07   ` Stephen Rothwell

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=20241024185007.GA968089@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=bhelgaas@google.com \
    --cc=kw@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.