From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
Jim Quinlan <jquinlan@broadcom.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: manual merge of the usb tree with the pci tree
Date: Mon, 21 Sep 2020 17:50:06 +0200 [thread overview]
Message-ID: <20200921155006.GB1023551@kroah.com> (raw)
In-Reply-To: <20200921151807.637905c0@canb.auug.org.au>
On Mon, Sep 21, 2020 at 03:18:07PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the usb tree got a conflict in:
>
> drivers/pci/controller/pcie-brcmstb.c
>
> between commit:
>
> 1cf1b0a6dd95 ("PCI: brcmstb: Add bcm7278 register info")
>
> from the pci tree and commit:
>
> f48cc509c935 ("Revert "PCI: brcmstb: Wait for Raspberry Pi's firmware when present"")
>
> from the usb 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/pci/controller/pcie-brcmstb.c
> index 6e7aa82a54a3,bac63d04297f..000000000000
> --- a/drivers/pci/controller/pcie-brcmstb.c
> +++ b/drivers/pci/controller/pcie-brcmstb.c
> @@@ -1213,8 -929,6 +1211,7 @@@ static int brcm_pcie_probe(struct platf
> {
> struct device_node *np = pdev->dev.of_node, *msi_np;
> struct pci_host_bridge *bridge;
> - struct device_node *fw_np;
> + const struct pcie_cfg_data *data;
> struct brcm_pcie *pcie;
> int ret;
>
Looks good to me, thanks!
greg k-h
next prev parent reply other threads:[~2020-09-21 15:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 5:18 linux-next: manual merge of the usb tree with the pci tree Stephen Rothwell
2020-09-21 15:50 ` Greg KH [this message]
2020-10-15 21:47 ` Stephen Rothwell
2020-10-16 7:26 ` Jim Quinlan
-- strict thread matches above, loose matches on Subject: below --
2019-06-24 7:12 Stephen Rothwell
2019-06-24 7:34 ` Greg KH
2019-06-24 7:47 ` Stephen Rothwell
2019-07-08 23:58 ` Stephen Rothwell
2019-07-09 6:35 ` Greg KH
2019-07-09 6:53 ` 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=20200921155006.GB1023551@kroah.com \
--to=greg@kroah.com \
--cc=bhelgaas@google.com \
--cc=jquinlan@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=nsaenzjulienne@suse.de \
--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