From: Alan Cox <alan@lxorguk•ukuu.org.uk>
To: Ingo Molnar <mingo@elte•hu>
Cc: Randy Dunlap <rdunlap@xenotime•net>,
Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
x86 maintainers <x86@kernel•org>
Subject: Re: linux-next: Tree for Sept 28 (mrst)
Date: Mon, 5 Dec 2011 19:10:33 +0000 [thread overview]
Message-ID: <20111205191033.191615af@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20111205184105.GA20121@elte.hu>
On Mon, 5 Dec 2011 19:41:05 +0100
Ingo Molnar <mingo@elte•hu> wrote:
>
> * Randy Dunlap <rdunlap@xenotime•net> wrote:
>
> > On 09/28/2011 03:11 PM, Randy Dunlap wrote:
> > > On 09/28/11 03:04, Stephen Rothwell wrote:
> > >> Hi all,
> > >
> > >
> > > When CONFIG_X86_INTEL_MID=y but CONFIG_X86_MRST is not enabled
> > > (this is on an i386/X86_32 build):
> > >
> > > rtc.c:(.init.text+0x6234): undefined reference to `__mrst_cpu_chip'
> > >
> > > Full randconfig file is attached.
> >
> > Hm, it's now 20111205 and this build error is still around.
> > Is there any hope for getting it fixed?
>
> Alan?
Don't think I saw the original report - I'll take a look. I imagine it's
just an X86_MRST that didn't get changed rightly.
next prev parent reply other threads:[~2011-12-05 19:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 10:04 linux-next: Tree for Sept 28 Stephen Rothwell
2011-09-28 22:11 ` linux-next: Tree for Sept 28 (mrst) Randy Dunlap
2011-12-05 18:39 ` Randy Dunlap
2011-12-05 18:41 ` Ingo Molnar
2011-12-05 19:10 ` Alan Cox [this message]
2011-09-28 22:29 ` linux-next: Tree for Sept 28 (media/video/mt9p031.c) Randy Dunlap
2011-09-28 22:31 ` Randy Dunlap
2011-09-30 21:34 ` [PATCH] drivers/media: fix dependencies in video mt9t001/mt9p031 Paul Gortmaker
2011-09-30 22:38 ` Randy Dunlap
2011-10-06 3:02 ` Stephen Rothwell
2011-10-08 10:52 ` Mauro Carvalho Chehab
2011-10-09 3:39 ` Paul Gortmaker
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=20111205191033.191615af@lxorguk.ukuu.org.uk \
--to=alan@lxorguk$(echo .)ukuu.org.uk \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@elte$(echo .)hu \
--cc=rdunlap@xenotime$(echo .)net \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=x86@kernel$(echo .)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