All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: <linux-kernel@vger.kernel.org>, <alsa-devel@alsa-project.org>,
	<tiwai@suse.com>
Subject: Re: [PATCH -next] ALSA: n64: check return value after calling platform_get_resource()
Date: Sat, 12 Jun 2021 09:31:25 +0200	[thread overview]
Message-ID: <s5hh7i35yk2.wl-tiwai@suse.de> (raw)
In-Reply-To: <20210610124958.116142-1-yangyingliang@huawei.com>

On Thu, 10 Jun 2021 14:49:58 +0200,
Yang Yingliang wrote:
> 
> It will cause null-ptr-deref if platform_get_resource() returns NULL,
> we need check the return value.
> 
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>

Thanks, applied.


Takashi

WARNING: multiple messages have this Message-ID (diff)
From: Takashi Iwai <tiwai@suse.de>
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
	tiwai@suse.com
Subject: Re: [PATCH -next] ALSA: n64: check return value after calling platform_get_resource()
Date: Sat, 12 Jun 2021 09:31:25 +0200	[thread overview]
Message-ID: <s5hh7i35yk2.wl-tiwai@suse.de> (raw)
In-Reply-To: <20210610124958.116142-1-yangyingliang@huawei.com>

On Thu, 10 Jun 2021 14:49:58 +0200,
Yang Yingliang wrote:
> 
> It will cause null-ptr-deref if platform_get_resource() returns NULL,
> we need check the return value.
> 
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>

Thanks, applied.


Takashi

  reply	other threads:[~2021-06-12  7:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-10 12:49 [PATCH -next] ALSA: n64: check return value after calling platform_get_resource() Yang Yingliang
2021-06-10 12:49 ` Yang Yingliang
2021-06-12  7:31 ` Takashi Iwai [this message]
2021-06-12  7:31   ` Takashi Iwai

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=s5hh7i35yk2.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tiwai@suse.com \
    --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 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.