From: Eduardo Valentin <edubezval@gmail.com>
To: Zhang Rui <rui.zhang@intel.com>
Cc: Shailendra Verma <shailendra.v@samsung.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
p.shailesh@samsung.com, ashish.kalra@samsung.com,
Shailendra Verma <shailendra.capricorn@gmail.com>
Subject: Re: [PATCH] Thermal - Fix possible NULL derefrence.
Date: Sat, 18 Feb 2017 17:27:30 -0800 [thread overview]
Message-ID: <20170219012728.GB28525@localhost.localdomain> (raw)
In-Reply-To: <1486438213.2645.1.camel@intel.com>
On Tue, Feb 07, 2017 at 11:30:13AM +0800, Zhang Rui wrote:
> Just one comment,
> the subject should be
> [PATCH] Thermal: imx_thermal : Fix possible NULL derefrence
I fixed the commit title, but I am taking this one
prev parent reply other threads:[~2017-02-19 1:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170130050525epcas1p3686ebf52f0215eef64a358338843305d@epcas1p3.samsung.com>
2017-01-30 5:04 ` [PATCH] Thermal - Fix possible NULL derefrence Shailendra Verma
2017-02-07 3:30 ` Zhang Rui
2017-02-19 1:27 ` Eduardo Valentin [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=20170219012728.GB28525@localhost.localdomain \
--to=edubezval@gmail.com \
--cc=ashish.kalra@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=p.shailesh@samsung.com \
--cc=rui.zhang@intel.com \
--cc=shailendra.capricorn@gmail.com \
--cc=shailendra.v@samsung.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).