All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: arm@kernel.org
Cc: linux-rockchip@lists.infradead.org, linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 3/3] Rockchip soc32 updates for 5.3 round 1
Date: Tue, 11 Jun 2019 10:55:28 +0200	[thread overview]
Message-ID: <6757963.JBp9oB5bj2@phil> (raw)
In-Reply-To: <3004130.oi6ZuZy1Zf@phil>

The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:

  Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v5.3-rockchip-soc32-1

for you to fetch changes up to c2af88f1a0cdf4cbe94b51fd93e52a3f55606a13:

  ARM: rockchip: fix missing of_node_put calls in smp code (2019-05-20 01:00:41 +0200)

----------------------------------------------------------------
Another missing of_node_put

----------------------------------------------------------------
Wen Yang (1):
      ARM: rockchip: fix missing of_node_put calls in smp code

 arch/arm/mach-rockchip/platsmp.c | 12 ++++++++++--
 arch/arm/mach-rockchip/pm.c      |  2 ++
 2 files changed, 12 insertions(+), 2 deletions(-)

WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: arm@kernel.org
Cc: linux-rockchip@lists.infradead.org, linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 3/3] Rockchip soc32 updates for 5.3 round 1
Date: Tue, 11 Jun 2019 10:55:28 +0200	[thread overview]
Message-ID: <6757963.JBp9oB5bj2@phil> (raw)
In-Reply-To: <3004130.oi6ZuZy1Zf@phil>

The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:

  Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v5.3-rockchip-soc32-1

for you to fetch changes up to c2af88f1a0cdf4cbe94b51fd93e52a3f55606a13:

  ARM: rockchip: fix missing of_node_put calls in smp code (2019-05-20 01:00:41 +0200)

----------------------------------------------------------------
Another missing of_node_put

----------------------------------------------------------------
Wen Yang (1):
      ARM: rockchip: fix missing of_node_put calls in smp code

 arch/arm/mach-rockchip/platsmp.c | 12 ++++++++++--
 arch/arm/mach-rockchip/pm.c      |  2 ++
 2 files changed, 12 insertions(+), 2 deletions(-)




_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2019-06-11  8:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-11  8:53 [GIT PULL 1/3] Rockchip dts32 updates for 5.3 round 1 Heiko Stuebner
2019-06-11  8:53 ` Heiko Stuebner
2019-06-11  8:54 ` [GIT PULL 2/3] Rockchip dts64 " Heiko Stuebner
2019-06-11  8:54   ` Heiko Stuebner
2019-06-19 13:22   ` Olof Johansson
2019-06-19 13:22     ` Olof Johansson
2019-06-11  8:55 ` Heiko Stuebner [this message]
2019-06-11  8:55   ` [GIT PULL 3/3] Rockchip soc32 " Heiko Stuebner
2019-06-17 12:14   ` Olof Johansson
2019-06-17 12:14     ` Olof Johansson
2019-06-19 13:22 ` [GIT PULL 1/3] Rockchip dts32 " Olof Johansson
2019-06-19 13:22   ` Olof Johansson

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=6757963.JBp9oB5bj2@phil \
    --to=heiko@sntech.de \
    --cc=arm@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-rockchip@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.