From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Arnd Bergmann <arnd@arndb.de>,
Florian Fainelli <f.fainelli@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Yang Yingliang <yangyingliang@huawei.com>,
Yuan Can <yuancan@huawei.com>
Subject: Re: linux-next: manual merge of the char-misc tree with the broadcom tree
Date: Fri, 25 Nov 2022 18:31:26 +0100 [thread overview]
Message-ID: <Y4D77ktgpDOLggM4@kroah.com> (raw)
In-Reply-To: <20221125112542.466ebc42@canb.auug.org.au>
On Fri, Nov 25, 2022 at 11:25:42AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the char-misc tree got a conflict in:
>
> drivers/firmware/raspberrypi.c
>
> between commit:
>
> 117bd98daca0 ("firmware: raspberrypi: Use dev_err_probe() to simplify code")
>
> from the broadcom tree and commit:
>
> 7b51161696e8 ("firmware: raspberrypi: fix possible memory leak in rpi_firmware_probe()")
>
> from the char-misc 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/firmware/raspberrypi.c
> index ec07bf26e5eb,dba315f675bc..000000000000
> --- a/drivers/firmware/raspberrypi.c
> +++ b/drivers/firmware/raspberrypi.c
> @@@ -288,9 -268,13 +288,11 @@@ static int rpi_firmware_probe(struct pl
> fw->cl.tx_block = true;
>
> fw->chan = mbox_request_channel(&fw->cl, 0);
> - if (IS_ERR(fw->chan))
> - return dev_err_probe(dev, PTR_ERR(fw->chan),
> - "Failed to get mbox channel\n");
> + if (IS_ERR(fw->chan)) {
> + int ret = PTR_ERR(fw->chan);
> - if (ret != -EPROBE_DEFER)
> - dev_err(dev, "Failed to get mbox channel: %d\n", ret);
> + kfree(fw);
> - return ret;
> ++ return dev_err_probe(dev, ret, "Failed to get mbox channel\n");
> + }
>
> init_completion(&fw->c);
> kref_init(&fw->consumers);
Looks good to me, thanks!
greg k-h
next prev parent reply other threads:[~2022-11-25 17:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 0:25 linux-next: manual merge of the char-misc tree with the broadcom tree Stephen Rothwell
2022-11-25 17:31 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-03 4:27 Stephen Rothwell
2025-06-03 5:11 ` Greg KH
2025-06-03 15:59 ` Florian Fainelli
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=Y4D77ktgpDOLggM4@kroah.com \
--to=greg@kroah.com \
--cc=arnd@arndb.de \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=yangyingliang@huawei.com \
--cc=yuancan@huawei.com \
/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;
as well as URLs for NNTP newsgroup(s).