From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] SCPI/Vexpress fixes for v4.8-rc
Date: Thu, 25 Aug 2016 17:11:43 -0700 [thread overview]
Message-ID: <20160826001143.GD6209@localhost> (raw)
In-Reply-To: <f232ba19-e359-3ef4-cce5-e76b0f35d078@arm.com>
Hi Sudeep,
On Tue, Aug 16, 2016 at 12:01:00PM +0100, Sudeep Holla wrote:
>
> 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)
This tag is signed with a key that I can't find any track of anywhere. The
32-bit ID is 317EE298. but the key you have on the servers is
0x39CFD4755FE2D5B4. What's going on?
After looking at the contents, it's harmless enough so I've stilled merged
it but please sort out your keys.
-Olof
next prev parent reply other threads:[~2016-08-26 0:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 11:01 [GIT PULL] SCPI/Vexpress fixes for v4.8-rc Sudeep Holla
2016-08-25 23:59 ` Olof Johansson
2016-08-26 0:11 ` Olof Johansson [this message]
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=20160826001143.GD6209@localhost \
--to=olof@lixom.net \
--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 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).