From: Darren Hart <dvhart@infradead.org>
To: Qipeng Zha <qipeng.zha@intel.com>
Cc: platform-driver-x86@vger.kernel.org,
andriy.shevchenko@linux.intel.com,
souvik.k.chakravarty@intel.com
Subject: Re: [PATCH] intel_punit_ipc: add NULL check for input parameters
Date: Thu, 14 Jan 2016 14:23:17 -0800 [thread overview]
Message-ID: <20160114222317.GC1989@malice.jf.intel.com> (raw)
In-Reply-To: <1452249147-34712-1-git-send-email-qipeng.zha@intel.com>
On Fri, Jan 08, 2016 at 06:32:27PM +0800, Qipeng Zha wrote:
> intel_punit_ipc_command() maybe called when in or out
> data pointers are NULL.
>
> Signed-off-by: Qipeng Zha <qipeng.zha@intel.com>
Queued, thank you Qipeng.
--
Darren Hart
Intel Open Source Technology Center
prev parent reply other threads:[~2016-01-14 22:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 10:32 [PATCH] intel_punit_ipc: add NULL check for input parameters Qipeng Zha
2016-01-08 11:26 ` One Thousand Gnomes
2016-01-11 17:52 ` Darren Hart
2016-01-12 3:59 ` Chakravarty, Souvik K
2016-01-14 22:22 ` Darren Hart
2016-01-14 22:23 ` Darren Hart [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=20160114222317.GC1989@malice.jf.intel.com \
--to=dvhart@infradead.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=qipeng.zha@intel.com \
--cc=souvik.k.chakravarty@intel.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