From: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>,
Colin Cross <ccross-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org>
Cc: Peter De Schrijver
<pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: [PATCH 0/2] arm/tegra: Fix section mismatch errors in pinmux
Date: Mon, 19 Dec 2011 11:01:56 -0700 [thread overview]
Message-ID: <1324317718-24464-1-git-send-email-swarren@nvidia.com> (raw)
Patches in Tegra's for-3.3/soc branch introduce some section mismatch
errors when building with CONFIG_DEBUG_SECTION_MISMATCH=y. This series
fixes them. I patched each file separately in case you want to squash
these into the original patches.
tegra20: 6996e08 arm/tegra: prepare pinmux code for multiple tegra variants
tegra30: 241682c arm/tegra: pinmux tables and definitions for tegra30
Stephen Warren (2):
arm/tegra: Fix section mismatch errors in tegra20 pinmux
arm/tegra: Fix section mismatch errors in tegra30 pinmux
arch/arm/mach-tegra/pinmux-tegra20-tables.c | 2 +-
arch/arm/mach-tegra/pinmux-tegra30-tables.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
next reply other threads:[~2011-12-19 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 18:01 Stephen Warren [this message]
[not found] ` <1324317718-24464-1-git-send-email-swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2011-12-19 18:01 ` [PATCH 1/2] arm/tegra: Fix section mismatch errors in tegra20 pinmux Stephen Warren
2011-12-19 18:01 ` [PATCH 2/2] arm/tegra: Fix section mismatch errors in tegra30 pinmux Stephen Warren
2011-12-20 2:05 ` [PATCH 0/2] arm/tegra: Fix section mismatch errors in pinmux Olof Johansson
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=1324317718-24464-1-git-send-email-swarren@nvidia.com \
--to=swarren-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=ccross-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org \
--cc=pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).