All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	kbuild test robot <lkp@intel.com>,
	Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH v3 2/2] software node: Initialize the return value in software_node_find_by_name()
Date: Wed, 4 Sep 2019 23:06:21 +0200	[thread overview]
Message-ID: <CAJZ5v0h_UUu8ATkK0t7ffSg6hQiFf0JsHYNTSGZeELkNrxoe5g@mail.gmail.com> (raw)
In-Reply-To: <20190904120732.GB15829@kroah.com>

On Wed, Sep 4, 2019 at 2:07 PM Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
>
> On Fri, Aug 30, 2019 at 10:51:56AM +0300, Heikki Krogerus wrote:
> > The software node is searched from a list that may be empty
> > when the function is called. This makes sure that the
> > function returns NULL if the list is empty.
> >
> > Fixes: 1666faedb567 ("software node: Add software_node_get_reference_args()")
> > Reported-by: kbuild test robot <lkp@intel.com>
> > Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
> > Signed-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
>
> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Applied, thanks!

      reply	other threads:[~2019-09-04 21:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-30  7:51 [PATCH v3 0/2] software nodes: Fix use of potentially uninitialized variable Heikki Krogerus
2019-08-30  7:51 ` [PATCH v3 1/2] software node: Initialize the return value in software_node_to_swnode() Heikki Krogerus
2019-09-04 12:07   ` Greg Kroah-Hartman
2019-09-04 21:03     ` Rafael J. Wysocki
2019-08-30  7:51 ` [PATCH v3 2/2] software node: Initialize the return value in software_node_find_by_name() Heikki Krogerus
2019-09-04 12:07   ` Greg Kroah-Hartman
2019-09-04 21:06     ` Rafael J. Wysocki [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=CAJZ5v0h_UUu8ATkK0t7ffSg6hQiFf0JsHYNTSGZeELkNrxoe5g@mail.gmail.com \
    --to=rafael@kernel.org \
    --cc=dan.carpenter@oracle.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@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 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.