All of lore.kernel.org
 help / color / mirror / Atom feed
From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] SCPI/Vexpress fixes for v4.8-rc
Date: Tue, 16 Aug 2016 12:01:00 +0100	[thread overview]
Message-ID: <f232ba19-e359-3ef4-cce5-e76b0f35d078@arm.com> (raw)


Hi ARM-SoC guys,

I have couple of missing of_node_put fixes in vexpress/scpi drivers.
I am not sure if these are considered as more cleanup patches rather
than fixes as OF reference counting is not something religiously checked
always. Let me know, I will move these to v4.9 queue otherwise.

-- 
Regards,
Sudeep

The following changes since commit 29b4817d4018df78086157ea3a55c1d9424a7cfc:

   Linux 4.8-rc1 (2016-08-07 18:18:00 -0700)

are available in the git repository at:

   git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git 
tags/vexpress-fixes-4.8-rc

for you to fetch changes up to b079bd555f6060cd6b435a1eb58ec3b8d255ebd0:

   firmware: arm_scpi: add missing of_node_put after calling 
of_parse_phandle (2016-08-08 14:31:09 +0100)

----------------------------------------------------------------
SCPI/Vexpress fixes for v4.8-rc

Couple of minor fixes to add missing of_node_put after calling
of_parse_phandle in SCPI and vexpress-config bus drivers(Peter Chen)

----------------------------------------------------------------
Peter Chen (2):
       bus: vexpress-config: add missing of_node_put after calling 
of_parse_phandle
       firmware: arm_scpi: add missing of_node_put after calling 
of_parse_phandle

  drivers/bus/vexpress-config.c | 1 +
  drivers/firmware/arm_scpi.c   | 5 +++--
  2 files changed, 4 insertions(+), 2 deletions(-)

             reply	other threads:[~2016-08-16 11:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-16 11:01 Sudeep Holla [this message]
2016-08-25 23:59 ` [GIT PULL] SCPI/Vexpress fixes for v4.8-rc Olof Johansson
2016-08-26  0:11 ` Olof Johansson
2016-08-26  9:38   ` Sudeep Holla

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=f232ba19-e359-3ef4-cce5-e76b0f35d078@arm.com \
    --to=sudeep.holla@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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.