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 1/3] randconfig build fix for omap soc changes for v5.6
Date: Fri, 24 Jan 2020 12:11:22 -0800 [thread overview]
Message-ID: <pull-1579896427-50330@atomide.com> (raw)
From: "Tony Lindgren" <tony@atomide.com>
The following changes since commit 8ab871f8bdfcca627802b6992e556fba5722a268:
ARM: OMAP2+: sleep43xx: Call secure suspend/resume handlers (2020-01-13 10:06:46 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v5.6/soc-build-fix-signed
for you to fetch changes up to c37baa06f8a970e4a533d41f7d33e5e57de5ad25:
ARM: OMAP2+: Fix undefined reference to omap_secure_init (2020-01-23 07:48:26 -0800)
----------------------------------------------------------------
Randconfig build fix for recent SoC changes for v5.6
We can get build failures if let's say if only am335x SoC is selected.
Let's fix this by always building secure-common.
----------------------------------------------------------------
Andrew F. Davis (1):
ARM: OMAP2+: Fix undefined reference to omap_secure_init
arch/arm/mach-omap2/Makefile | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: soc@kernel.org
Cc: Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org, arm@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/3] randconfig build fix for omap soc changes for v5.6
Date: Fri, 24 Jan 2020 12:11:22 -0800 [thread overview]
Message-ID: <pull-1579896427-50330@atomide.com> (raw)
From: "Tony Lindgren" <tony@atomide.com>
The following changes since commit 8ab871f8bdfcca627802b6992e556fba5722a268:
ARM: OMAP2+: sleep43xx: Call secure suspend/resume handlers (2020-01-13 10:06:46 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v5.6/soc-build-fix-signed
for you to fetch changes up to c37baa06f8a970e4a533d41f7d33e5e57de5ad25:
ARM: OMAP2+: Fix undefined reference to omap_secure_init (2020-01-23 07:48:26 -0800)
----------------------------------------------------------------
Randconfig build fix for recent SoC changes for v5.6
We can get build failures if let's say if only am335x SoC is selected.
Let's fix this by always building secure-common.
----------------------------------------------------------------
Andrew F. Davis (1):
ARM: OMAP2+: Fix undefined reference to omap_secure_init
arch/arm/mach-omap2/Makefile | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-01-24 20:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 20:11 Tony Lindgren [this message]
2020-01-24 20:11 ` [GIT PULL 1/3] randconfig build fix for omap soc changes for v5.6 Tony Lindgren
2020-01-24 20:11 ` [GIT PULL 2/3] ti-sysc changes for omap4 & 5 crypto Tony Lindgren
2020-01-24 20:11 ` Tony Lindgren
2020-01-24 20:11 ` [GIT PULL 3/3] late dts changes for omaps for v5.6 Tony Lindgren
2020-01-24 20:11 ` Tony Lindgren
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-1579896427-50330@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 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.