From: Nishanth Menon <nm@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: OMAP2+: Fix am4 only build after genpd changes
Date: Fri, 27 Nov 2020 08:45:02 -0600 [thread overview]
Message-ID: <20201127144502.of7okggrpvf5rbtz@evaluate> (raw)
In-Reply-To: <20201127063245.62153-1-tony@atomide.com>
On 08:32-20201127, Tony Lindgren wrote:
> With commit df6c2ec872a6 ("ARM: OMAP2+: Drop legacy remaining legacy
> platform data for am4") we moved am4 to boot with simple-pm-bus using
> genpd and devicetree based data. But I forgot to test am4 only build
> that still has few references to the old platform data left, and cause
> undefined reference errors with omap_hwmod_set_postsetup_state and
> omap_hwmod_for_each. We can just drop the related calls for am4 now,
> and also drop the references to unused struct wkup_m3_platform_data.
>
> Reported-by: Nishanth Menon <nm@ti.com>
> Signed-off-by: Tony Lindgren <tony@atomide.com>
> ---
>
> I'm applying this into omap-for-v5.11/genpd branch to fix build for
> am4 config.
Thanks Tony.
Tested-by: Nishanth Menon <nm@ti.com>
Tested against next-20201127 with .config
https://pastebin.ubuntu.com/p/qYwWH9FhW6/
[...]
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-11-27 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 6:32 [PATCH] ARM: OMAP2+: Fix am4 only build after genpd changes Tony Lindgren
2020-11-27 14:45 ` Nishanth Menon [this message]
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=20201127144502.of7okggrpvf5rbtz@evaluate \
--to=nm@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/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