From: David Miller <davem@davemloft.net>
To: dan.carpenter@oracle.com
Cc: tushar.n.dave@oracle.com, tiwai@suse.com, perex@perex.cz,
thomas.tai@oracle.com, alsa-devel@alsa-project.org,
sparclinux@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] dbri: move dereference after check for NULL
Date: Tue, 06 Dec 2016 12:19:35 -0500 (EST) [thread overview]
Message-ID: <20161206.121935.749414738010277977.davem@davemloft.net> (raw)
In-Reply-To: <20161201054830.GA20077@mwanda>
From: Dan Carpenter <dan.carpenter@oracle.com>
Date: Thu, 1 Dec 2016 08:48:30 +0300
> We accidentally introduced a dereference before the NULL check in
> xmit_descs() as part of silencing a GCC warning.
>
> Fixes: 16f46050e709 ("dbri: Fix compiler warning")
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Applied, thanks Dan.
prev parent reply other threads:[~2016-12-06 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 5:48 [patch] dbri: move dereference after check for NULL Dan Carpenter
2016-12-01 6:14 ` tndave
2016-12-06 17:19 ` David Miller [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=20161206.121935.749414738010277977.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alsa-devel@alsa-project.org \
--cc=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=perex@perex.cz \
--cc=sparclinux@vger.kernel.org \
--cc=thomas.tai@oracle.com \
--cc=tiwai@suse.com \
--cc=tushar.n.dave@oracle.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).