From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL v2] ARM: arm-soc fixes for 3.8
Date: Thu, 20 Dec 2012 10:45:25 -0800 [thread overview]
Message-ID: <20121220184525.GC21056@atomide.com> (raw)
In-Reply-To: <CAOesGMgxXmXUW2RP_5AxJ6Z5sRBhFJ2CQz4S12MwXAb3=ibYOA@mail.gmail.com>
* Olof Johansson <olof@lixom.net> [121220 10:11]:
>
> Yep, I forgot to bring the fixes branch into our for-next. Try again
> once it mirrors out, I just pushed out a rebuild of it. New top commit
> should be e691d77e8825054376b31e79a9b5f9fa79fe764d.
>
> I'm doing a "build all defconfigs" run before sending the incremental
> pull request of fixes to Linus.
Commit e691d77e8825054376b31e79a9b5f9fa79fe764d builds and
boots with my testconfigs.
I'm seeing the "BUG: spinlock bad magic on CPU#0" issue
reported and fixed here:
http://marc.info/?l=linux-arm-kernel&m=135594868503683&w=2
But that's probably been already posted as a proper patch
somewhere?
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Olof Johansson <olof@lixom.net>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
torvalds@linux-foundation.org, arm@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, maxime.ripard@free-electrons.com
Subject: Re: [GIT PULL v2] ARM: arm-soc fixes for 3.8
Date: Thu, 20 Dec 2012 10:45:25 -0800 [thread overview]
Message-ID: <20121220184525.GC21056@atomide.com> (raw)
In-Reply-To: <CAOesGMgxXmXUW2RP_5AxJ6Z5sRBhFJ2CQz4S12MwXAb3=ibYOA@mail.gmail.com>
* Olof Johansson <olof@lixom.net> [121220 10:11]:
>
> Yep, I forgot to bring the fixes branch into our for-next. Try again
> once it mirrors out, I just pushed out a rebuild of it. New top commit
> should be e691d77e8825054376b31e79a9b5f9fa79fe764d.
>
> I'm doing a "build all defconfigs" run before sending the incremental
> pull request of fixes to Linus.
Commit e691d77e8825054376b31e79a9b5f9fa79fe764d builds and
boots with my testconfigs.
I'm seeing the "BUG: spinlock bad magic on CPU#0" issue
reported and fixed here:
http://marc.info/?l=linux-arm-kernel&m=135594868503683&w=2
But that's probably been already posted as a proper patch
somewhere?
Regards,
Tony
next prev parent reply other threads:[~2012-12-20 18:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 16:38 [GIT PULL v2] ARM: arm-soc fixes for 3.8 Olof Johansson
2012-12-20 16:38 ` Olof Johansson
2012-12-20 16:49 ` Linus Torvalds
2012-12-20 16:49 ` Linus Torvalds
2012-12-20 17:28 ` Olof Johansson
2012-12-20 17:28 ` Olof Johansson
2012-12-20 17:35 ` Tony Lindgren
2012-12-20 17:35 ` Tony Lindgren
2012-12-20 17:44 ` Linus Torvalds
2012-12-20 17:44 ` Linus Torvalds
2012-12-20 17:56 ` Russell King - ARM Linux
2012-12-20 17:56 ` Russell King - ARM Linux
2012-12-20 18:08 ` Olof Johansson
2012-12-20 18:08 ` Olof Johansson
2012-12-20 18:45 ` Tony Lindgren [this message]
2012-12-20 18:45 ` Tony Lindgren
2012-12-20 19:00 ` Linus Torvalds
2012-12-20 19:00 ` Linus Torvalds
2012-12-20 19:08 ` Tony Lindgren
2012-12-20 19:08 ` Tony Lindgren
2012-12-20 19:50 ` [PATCH] ARM: OMAP2+: Trivial fix for IOMMU merge issue (Re: [GIT PULL v2] ARM: arm-soc fixes for 3.8) Tony Lindgren
2012-12-20 19:50 ` Tony Lindgren
2012-12-21 2:43 ` [GIT PULL v2] ARM: arm-soc fixes for 3.8 Benjamin Herrenschmidt
2012-12-21 2:43 ` Benjamin Herrenschmidt
2012-12-20 18:47 ` Russell King - ARM Linux
2012-12-20 18:47 ` Russell King - ARM Linux
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=20121220184525.GC21056@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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.