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/2] Renesas SoC updates for v6.8 (take two)
Date: Fri, 15 Dec 2023 13:15:19 +0100 [thread overview]
Message-ID: <cover.1702642338.git.geert+renesas@glider.be> (raw)
Hi SoC folks,
This is my second pull request for the inclusion of Renesas SoC updates
for v6.8.
It consists of 2 parts:
[GIT PULL 1/2] Renesas driver updates for v6.8
- Remove duplicate setup of soc_device_attribute.family,
- Make RZ/Five depend on !DMA_DIRECT_REMAP.
[GIT PULL 2/2] Renesas DTS updates for v6.8 (take two)
- Add IA55 interrupt controller and Ethernet support for the RZ/G3S
SoC and the RZ/G3S SMARC SoM,
- Miscellaneous fixes and improvements.
Thanks for pulling!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
WARNING: multiple messages have this Message-ID (diff)
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/2] Renesas SoC updates for v6.8 (take two)
Date: Fri, 15 Dec 2023 13:15:19 +0100 [thread overview]
Message-ID: <cover.1702642338.git.geert+renesas@glider.be> (raw)
Hi SoC folks,
This is my second pull request for the inclusion of Renesas SoC updates
for v6.8.
It consists of 2 parts:
[GIT PULL 1/2] Renesas driver updates for v6.8
- Remove duplicate setup of soc_device_attribute.family,
- Make RZ/Five depend on !DMA_DIRECT_REMAP.
[GIT PULL 2/2] Renesas DTS updates for v6.8 (take two)
- Add IA55 interrupt controller and Ethernet support for the RZ/G3S
SoC and the RZ/G3S SMARC SoM,
- Miscellaneous fixes and improvements.
Thanks for pulling!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-12-15 14:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 12:15 Geert Uytterhoeven [this message]
2023-12-15 12:15 ` [GIT PULL 1/2] Renesas SoC updates for v6.8 (take two) Geert Uytterhoeven
2023-12-15 12:15 ` [GIT PULL 1/2] Renesas driver updates for v6.8 Geert Uytterhoeven
2023-12-15 12:15 ` Geert Uytterhoeven
2023-12-21 17:41 ` patchwork-bot+linux-soc
2023-12-22 12:01 ` patchwork-bot+linux-soc
2023-12-15 12:15 ` [GIT PULL 2/2] Renesas DTS updates for v6.8 (take two) Geert Uytterhoeven
2023-12-15 12:15 ` 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.1702642338.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 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.