From: Tony Lindgren <tony@atomide.com>
To: soc@kernel.org
Cc: arm@kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"Tony Lindgren" <tony@atomide.com>
Subject: [GIT PULL] Clean-up for omaps for v6.4
Date: Thu, 30 Mar 2023 15:45:22 +0300 [thread overview]
Message-ID: <pull-1680180293-92168@atomide.com> (raw)
From: "Tony Lindgren" <tony@atomide.com>
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/tmlind/linux-omap tags/omap-for-v6.4/cleanup-signed
for you to fetch changes up to 19050da1d1057a7bc73fd9039f94b7f63a00e54e:
ARM: OMAP2+: hwmod: Use kzalloc for allocating only one element (2023-03-28 08:45:55 +0300)
----------------------------------------------------------------
Clean-up for omaps for v6.4
Some clean-up changes for omaps mostly to use of_property_read_bool() and
of_address_to_resource(). Also included is removal for an obsolete Kconfig
option, a typo fix, a return path change for am33xx_suspend_init(), and a
change to use kzalloc instead of kcalloc for a single element.
----------------------------------------------------------------
Jilin Yuan (1):
ARM: OMAP2+: fix repeated words in comments
Kenneth Lee (1):
ARM: OMAP2+: hwmod: Use kzalloc for allocating only one element
Lukas Bulwahn (1):
ARM: OMAP2+: remove obsolete config OMAP3_SDRC_AC_TIMING
Rob Herring (2):
ARM: OMAP2+: Use of_property_read_bool() for boolean properties
ARM: OMAP2+: Use of_address_to_resource()
ye xingchen (1):
ARM: OMAP2+: Remove the unneeded result variable
arch/arm/mach-omap2/Kconfig | 11 -----------
arch/arm/mach-omap2/cm33xx.c | 2 +-
arch/arm/mach-omap2/omap_hwmod.c | 23 ++++++++++-------------
arch/arm/mach-omap2/pm33xx-core.c | 6 +-----
4 files changed, 12 insertions(+), 30 deletions(-)
reply other threads:[~2023-03-30 12:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=pull-1680180293-92168@atomide.com \
--to=tony@atomide.com \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.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