From: Arnd Bergmann <arnd@arndb.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Nicolas Pitre <nicolas.pitre@linaro.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Russell King <rmk@arm.linux.org.uk>
Subject: Re: [GIT PULL] arm-soc new features (part 2/2) for 3.1
Date: Wed, 27 Jul 2011 17:07:53 +0200 [thread overview]
Message-ID: <201107271707.54059.arnd@arndb.de> (raw)
In-Reply-To: <CA+55aFygBzynb_4kZQEHQAU0Np0H9UCBFoW1hoRJ571QCMo42Q@mail.gmail.com>
On Wednesday 27 July 2011, Linus Torvalds wrote:
> I compared the end result with yours, and we did some things a bit
> differently, but on the whole it looks pretty identical. We have a
> different resolution for "exynos4_cpu_suspend()", but afaik mine is
> better (it looks like from a type standpoint it should return int, but
> due to the panic it doesn't matter). And we did those
> OMAP4430_DLL_OVERRIDE_SHIFT/MASK defines in a different order. I have
> some other changes in my tree (Andrew's patch-set for asm/atomic.h
> etc), so that makes for other differences in arch/arm, but it looks
> like it's ok.
>
> But you should double-check. I didn't compile-test any of it, I don't
> do the cross-compile thing, and maybe I missed something.
Looks all good as far as I can tell. Your exynos4_cpu_suspend is
better than the solution I had in next and everything else
is equivalent.
I'm still in the process of fixing randconfig builds that have never
been working for most arm platforms, so I can do a better job
at automatically doing build tests myself. My guess is that there
will be several build regressions due to stuff coming in but that
they are not the result of mismerges.
Arnd
prev parent reply other threads:[~2011-07-27 15:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 22:24 [GIT PULL] arm-soc new SOCs for 3.1 Arnd Bergmann
2011-07-26 22:31 ` [GIT PULL] arm-soc bug fixes (part 2) " Arnd Bergmann
2011-07-26 22:36 ` [GIT PULL] arm-soc cross-platform cleanups " Arnd Bergmann
2011-07-26 23:01 ` [GIT PULL] arm-soc new board support " Arnd Bergmann
2011-07-26 23:25 ` [GIT PULL] arm-soc new features (part 1/2) " Arnd Bergmann
2011-07-26 23:36 ` [GIT PULL] arm-soc new features (part 2/2) " Arnd Bergmann
2011-07-27 0:51 ` Linus Torvalds
2011-07-27 15:07 ` Arnd Bergmann [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=201107271707.54059.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=rmk@arm.linux.org.uk \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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