public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] bus: vexpress-config: fix device reference leak
Date: Wed, 30 Nov 2016 23:31:21 +0100	[thread overview]
Message-ID: <7686444.YJLCo5m10k@wuerfel> (raw)
In-Reply-To: <1479317491-7435-1-git-send-email-sudeep.holla@arm.com>

On Wednesday, November 16, 2016 5:31:30 PM CET Sudeep Holla wrote:
> From: Johan Hovold <johan@kernel.org>
> 
> Make sure to drop the reference to the parent device taken by
> class_find_device() after populating the bus.
> 
> Fixes: 3b9334ac835b ("mfd: vexpress: Convert custom func API to regmap")
> Acked-by: Sudeep Holla <sudeep.holla@arm.com>
> Signed-off-by: Johan Hovold <johan@kernel.org>
> ---
>  drivers/bus/vexpress-config.c | 7 ++++++-
>  1 file changed, 6 insertions(+), 1 deletion(-)
> 
> Hi ARM-SoC team,
> 
> I am not sure if these couple of patches can be considered as fixes for
> v4.9. I will leave that to you guys.
> 
> Can you pick these couple of patches directly either for v4.9 or v4.10 ?
> I am trying to avoid single patch pull requests here. Let me know if
> you prefer PR instead.
> 

Sorry for the delay. I think it's find to wait till 4.10, so
I've applied it to next/fixes-non-critical.

	Arnd

      parent reply	other threads:[~2016-11-30 22:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-16 17:31 [PATCH 1/2] bus: vexpress-config: fix device reference leak Sudeep Holla
2016-11-16 17:31 ` [PATCH 2/2] arm64: dts: juno: fix cluster sleep state entry latency on all SoC versions Sudeep Holla
2016-12-01 10:11   ` Sudeep Holla
2016-12-02 16:30     ` Arnd Bergmann
2016-11-28 13:57 ` [PATCH 1/2] bus: vexpress-config: fix device reference leak Sudeep Holla
2016-11-30 22:31 ` Arnd Bergmann [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=7686444.YJLCo5m10k@wuerfel \
    --to=arnd@arndb.de \
    --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