From: tony@atomide•com (Tony Lindgren)
To: linux-arm-kernel@lists•infradead.org
Subject: multiple linux-next OMAP3 build errors
Date: Fri, 1 Oct 2010 09:57:37 -0700 [thread overview]
Message-ID: <20101001165737.GT3117@atomide.com> (raw)
In-Reply-To: <AANLkTim9v1Y2o9QebYcJkh+QLVQq9fFOFE5P+OoyUHXa@mail.gmail.com>
* Grazvydas Ignotas <notasas@gmail•com> [101001 08:49]:
> hi,
>
> I've been building linux-next for a while now and keep getting these
> build errors, just posting them here in case not all are known. Not
> familiar enough with that code to send patches unfortunately.
>
> AS arch/arm/mm/proc-v7.o
> arch/arm/mm/proc-v7.S: Assembler messages:
> arch/arm/mm/proc-v7.S:363: Error: undefined symbol `PMD_FLAGS' in operation
This I've already fixed in omap-testing branch. Should get merged into
for-next soonish.
Regards,
Tony
next prev parent reply other threads:[~2010-10-01 16:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-01 15:57 multiple linux-next OMAP3 build errors Grazvydas Ignotas
2010-10-01 16:12 ` Anand Gadiyar
2010-10-01 16:57 ` Tony Lindgren [this message]
2010-10-04 6:29 ` Tomi Valkeinen
2010-10-04 11:04 ` Gadiyar, Anand
2010-10-04 22:30 ` Benjamin Herrenschmidt
2010-10-04 22:43 ` Yinghai Lu
2010-10-06 4:28 ` Yinghai Lu
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=20101001165737.GT3117@atomide.com \
--to=tony@atomide$(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