From: Dinh Nguyen <dinguyen@kernel.org>
To: arm@kernel.org, soc@kernel.org
Cc: dinguyen@kernel.org
Subject: [GIT PULL] ARM: socfpga: update for v6.6
Date: Tue, 22 Aug 2023 21:18:10 -0500 [thread overview]
Message-ID: <20230823021810.958072-1-dinguyen@kernel.org> (raw)
The following changes since commit 06c2afb862f9da8dc5efa4b6076a0e48c3fbaaa5:
Linux 6.5-rc1 (2023-07-09 13:53:13 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git tags/socfpga_update_for_v6.6
for you to fetch changes up to 37e2d7d23765c3948e21cb361100f1baeb65f4f3:
ARM: socfpga: Explicitly include correct DT includes (2023-07-20 14:38:38 -0500)
----------------------------------------------------------------
SoCFPGA mach update for v6.6
- Clean up DT includes in mach-socfpga
----------------------------------------------------------------
Rob Herring (1):
ARM: socfpga: Explicitly include correct DT includes
arch/arm/mach-socfpga/l2_cache.c | 2 +-
arch/arm/mach-socfpga/ocram.c | 4 +---
arch/arm/mach-socfpga/pm.c | 2 ++
arch/arm/mach-socfpga/socfpga.c | 4 +---
4 files changed, 5 insertions(+), 7 deletions(-)
next reply other threads:[~2023-08-23 2:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 2:18 Dinh Nguyen [this message]
2023-08-29 20:20 ` [GIT PULL] ARM: socfpga: update for v6.6 patchwork-bot+linux-soc
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=20230823021810.958072-1-dinguyen@kernel.org \
--to=dinguyen@kernel.org \
--cc=arm@kernel.org \
--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