public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vasant Hegde <hegdevasant@linux.vnet.ibm.com>
To: Saurabh Sengar <saurabh.truth@gmail.com>,
	rpurdie@rpsys.net, j.anaszewski@samsung.com,
	linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] leds/powernv : removing NULL check
Date: Wed, 25 Nov 2015 20:14:31 +0530	[thread overview]
Message-ID: <5655C94F.4070504@linux.vnet.ibm.com> (raw)
In-Reply-To: <1448270896-23955-1-git-send-email-saurabh.truth@gmail.com>

On 11/23/2015 02:58 PM, Saurabh Sengar wrote:
> no need to explicitly check for pointer to be null,
> of_prop_next_string anyways return NULL, if passed pointer is NULL
> and hence loop will continue

Thanks! Patch looks good.

-Vasant


  parent reply	other threads:[~2015-11-25 14:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-23  9:28 [PATCH] leds/powernv : removing NULL check Saurabh Sengar
2015-11-23 12:37 ` Jacek Anaszewski
2015-11-25 14:44 ` Vasant Hegde [this message]
2015-11-25 15:17   ` Jacek Anaszewski
2015-11-25 16:42     ` Vasant Hegde

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=5655C94F.4070504@linux.vnet.ibm.com \
    --to=hegdevasant@linux.vnet.ibm.com \
    --cc=j.anaszewski@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=rpurdie@rpsys.net \
    --cc=saurabh.truth@gmail.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