From: mmayer@broadcom•com (Markus Mayer)
To: linux-arm-kernel@lists•infradead.org
Subject: vexpress compilation error in next-20121127
Date: Thu, 29 Nov 2012 12:03:29 -0800 [thread overview]
Message-ID: <50B7BF91.1070705@broadcom.com> (raw)
In-Reply-To: <1354189196.2987.59.camel@hornet>
On 12-11-29 03:39 AM, Pawel Moll wrote:
>>
>> Is there a quick way to describe the difference between these two
>> branches? I am okay to use for-next rather than next/soc, but I would
>> like to know what the difference between the two.
>
> Those are questions to Arnd and Olof [...]
Thanks for your help. I have started a new thread for this topic.
Regards,
-Markus
next prev parent reply other threads:[~2012-11-29 20:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 1:16 vexpress compilation error in next-20121127 Markus Mayer
2012-11-28 12:36 ` Pawel Moll
2012-11-28 20:53 ` Markus Mayer
2012-11-29 11:39 ` Pawel Moll
2012-11-29 20:03 ` Markus Mayer [this message]
2012-12-13 19:07 ` Behan Webster
2012-12-14 9:49 ` Pawel Moll
2012-12-14 14:47 ` Behan Webster
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=50B7BF91.1070705@broadcom.com \
--to=mmayer@broadcom$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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