From: Vinod Koul <vkoul@kernel.org>
To: Yu Kuai <yukuai3@huawei.com>
Cc: dan.j.williams@intel.com, anup.patel@broadcom.com,
ray.jui@broadcom.com, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org, yi.zhang@huawei.com
Subject: Re: [PATCH V2] dmaengine: bcm-sba-raid: add missing put_device() call in sba_probe()
Date: Mon, 17 Aug 2020 10:47:45 +0530 [thread overview]
Message-ID: <20200817051745.GG2639@vkoul-mobl> (raw)
In-Reply-To: <20200729124904.2541801-1-yukuai3@huawei.com>
On 29-07-20, 20:49, Yu Kuai wrote:
> if of_find_device_by_node() succeed, sba_probe() doesn't have a
> corresponding put_device(). Thus add a jump target to fix the
> exception handling for this function implementation.
Applied, thanks
--
~Vinod
next prev parent reply other threads:[~2020-08-17 5:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 12:49 [PATCH V2] dmaengine: bcm-sba-raid: add missing put_device() call in sba_probe() Yu Kuai
2020-08-17 5:17 ` Vinod Koul [this message]
2020-07-29 18:00 Markus Elfring
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=20200817051745.GG2639@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=anup.patel@broadcom.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ray.jui@broadcom.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai3@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).