From: Kalle Valo <kvalo@codeaurora.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Miles Hu <milehu@codeaurora.org>,
kernel-janitors@vger.kernel.org,
Venkateswara Naralasetty <vnaralas@codeaurora.org>,
linux-wireless@vger.kernel.org,
Muna Sinada <msinada@codeaurora.org>,
Shashidhar Lakkavalli <slakkavalli@datto.com>,
ath11k@lists.infradead.org
Subject: Re: [PATCH] ath11k: checking for NULL vs IS_ERR()
Date: Wed, 18 Dec 2019 17:55:56 +0000 (UTC) [thread overview]
Message-ID: <20191218175556.AA276C4479F@smtp.codeaurora.org> (raw)
In-Reply-To: <20191213105127.kijiazxwtghmubyk@kili.mountain>
Dan Carpenter <dan.carpenter@oracle.com> wrote:
> The ath11k_ce_alloc_ring() function returns error pointers on error, not
> NULL. The rest of the driver assumes that "pipe->src_ring" is either
> valid or NULL so this patch introduces a temporary varaible to avoid
> leaving it as an error pointer.
>
> Fixes: d5c65159f289 ("ath11k: driver for Qualcomm IEEE 802.11ax devices")
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Patch applied to ath-next branch of ath.git, thanks.
c76fa846b0e1 ath11k: checking for NULL vs IS_ERR()
--
https://patchwork.kernel.org/patch/11290421/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
prev parent reply other threads:[~2019-12-18 17:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 10:51 [PATCH] ath11k: checking for NULL vs IS_ERR() Dan Carpenter
2019-12-13 10:51 ` Dan Carpenter
2019-12-13 10:51 ` Dan Carpenter
2019-12-18 17:55 ` Kalle Valo
2019-12-18 17:55 ` Kalle Valo
2019-12-18 17:55 ` Kalle Valo [this message]
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=20191218175556.AA276C4479F@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=milehu@codeaurora.org \
--cc=msinada@codeaurora.org \
--cc=slakkavalli@datto.com \
--cc=vnaralas@codeaurora.org \
/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.