From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Mike Turquette <mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>,
Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] clk: tegra: fix ifdef for tegra_periph_reset_assert inline
Date: Thu, 27 Jun 2013 16:59:04 -0600 [thread overview]
Message-ID: <51CCC3B8.80909@wwwdotorg.org> (raw)
In-Reply-To: <20130624210333.23972.95491@quantum>
On 06/24/2013 03:03 PM, Mike Turquette wrote:
> Quoting Stephen Warren (2013-06-24 12:05:56)
>> From: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
>>
>> Commit 7064f6b "clk: tegra: provide tegra_periph_reset_assert
>> alternative" added ifdef'd static inline versions of some functions,
>> but tested ARCH_TEGRA rather than CONFIG_ARCH_TEGRA, thus disabling
>> these function in all cases. In some cases, this caused HW modules to
>> misbehave; for example, the Tegra I2C driver BUG()d during boot on
>> Seaboard.
>>
>> Reported-by: Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>
>> Signed-off-by: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
>
> Thanks for the fixup. I had already published the offending commit and
> can't rebase it, so I just applied this patch on top.
>
> Pulled into clk-next for 3.11.
Did that get pushed out to the git server? The patch isn't in next-20130627.
next prev parent reply other threads:[~2013-06-27 22:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 19:05 [PATCH] clk: tegra: fix ifdef for tegra_periph_reset_assert inline Stephen Warren
2013-06-24 21:03 ` Mike Turquette
2013-06-27 22:59 ` Stephen Warren [this message]
2013-06-28 22:29 ` Mike Turquette
[not found] ` <1372100756-10448-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-06-24 21:07 ` Paul Walmsley
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=51CCC3B8.80909@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org \
--cc=swarren-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