Linux Renesas SOC kernel development
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert+renesas@glider.be>
To: arm-soc <arm@kernel.org>, soc <soc@kernel.org>
Cc: Magnus Damm <magnus.damm@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-renesas-soc@vger.kernel.org,
	Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [GIT PULL 1/3] Renesas ARM SoC updates for v6.4
Date: Mon, 10 Apr 2023 09:55:26 +0200	[thread overview]
Message-ID: <cover.1681113113.git.geert+renesas@glider.be> (raw)
In-Reply-To: <cover.1681113111.git.geert+renesas@glider.be>

The following changes since commit fe15c26ee26efa11741a7b632e9f23b01aca4cc6:

  Linux 6.3-rc1 (2023-03-05 14:52:03 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git tags/renesas-arm-soc-for-v6.4-tag1

for you to fetch changes up to 6050cb1c7ad40b5673cd6ee7cfd36db3ca9be5fe:

  ARM: sh-mobile: Use of_cpu_node_to_id() to read CPU node 'reg' (2023-03-30 16:02:42 +0200)

----------------------------------------------------------------
Renesas ARM SoC updates for v6.4

  - Use of_cpu_node_to_id() to read CPU node 'reg'.

----------------------------------------------------------------
Rob Herring (1):
      ARM: sh-mobile: Use of_cpu_node_to_id() to read CPU node 'reg'

 arch/arm/mach-shmobile/platsmp-apmu.c | 36 ++++++++++++++++-------------------
 1 file changed, 16 insertions(+), 20 deletions(-)

  reply	other threads:[~2023-04-10  7:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-10  7:55 [GIT PULL 0/3] Renesas SoC updates for v6.4 (take two) Geert Uytterhoeven
2023-04-10  7:55 ` Geert Uytterhoeven [this message]
2023-04-10  7:55 ` [GIT PULL 2/3] Renesas driver " Geert Uytterhoeven
2023-04-10  7:55 ` [GIT PULL 3/3] Renesas DTS " Geert Uytterhoeven

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=cover.1681113113.git.geert+renesas@glider.be \
    --to=geert+renesas@glider.be \
    --cc=arm@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=soc@kernel.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