From: Stephan Gerhold <stephan@gerhold.net>
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-arm-msm@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH -next] net: wwan: qcom_bam_dmux: fix wrong pointer passed to IS_ERR()
Date: Sat, 19 Mar 2022 12:38:13 +0100 [thread overview]
Message-ID: <YjXApWvAnGUeTpPt@gerhold.net> (raw)
In-Reply-To: <20220319032450.3288224-1-yangyingliang@huawei.com>
On Sat, Mar 19, 2022 at 11:24:50AM +0800, Yang Yingliang wrote:
> It should check dmux->tx after calling dma_request_chan().
>
> Fixes: 21a0ffd9b38c ("net: wwan: Add Qualcomm BAM-DMUX WWAN network driver")
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
Good catch, thanks!
Reviewed-by: Stephan Gerhold <stephan@gerhold.net>
I'm a bit confused by the -next suffix in the subject though,
this should probably go into "net" (not "net-next") since it is a fix.
> ---
> drivers/net/wwan/qcom_bam_dmux.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/wwan/qcom_bam_dmux.c b/drivers/net/wwan/qcom_bam_dmux.c
> index 5dfa2eba6014..17d46f4d2913 100644
> --- a/drivers/net/wwan/qcom_bam_dmux.c
> +++ b/drivers/net/wwan/qcom_bam_dmux.c
> @@ -755,7 +755,7 @@ static int __maybe_unused bam_dmux_runtime_resume(struct device *dev)
> return 0;
>
> dmux->tx = dma_request_chan(dev, "tx");
> - if (IS_ERR(dmux->rx)) {
> + if (IS_ERR(dmux->tx)) {
> dev_err(dev, "Failed to request TX DMA channel: %pe\n", dmux->tx);
> dmux->tx = NULL;
> bam_dmux_runtime_suspend(dev);
> --
> 2.25.1
>
next prev parent reply other threads:[~2022-03-19 11:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-19 3:24 [PATCH -next] net: wwan: qcom_bam_dmux: fix wrong pointer passed to IS_ERR() Yang Yingliang
2022-03-19 11:38 ` Stephan Gerhold [this message]
2022-03-22 8:50 ` patchwork-bot+netdevbpf
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=YjXApWvAnGUeTpPt@gerhold.net \
--to=stephan@gerhold.net \
--cc=davem@davemloft.net \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yangyingliang@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).