From: Greg KH <gregkh@linuxfoundation.org>
To: "Sven Köhler" <sven.koehler@gmail.com>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Linux 3.7.4
Date: Thu, 24 Jan 2013 10:17:26 -0800 [thread overview]
Message-ID: <20130124181726.GD12106@kroah.com> (raw)
In-Reply-To: <51009E68.90407@gmail.com>
On Thu, Jan 24, 2013 at 03:37:28AM +0100, Sven K�hler wrote:
> Am 24.01.2013 03:24, schrieb Greg KH:
> > On Thu, Jan 24, 2013 at 03:06:29AM +0100, Sven K�hler wrote:
> >> Hi,
> >>
> >> I had to revert this, because it resulted in
> >>
> >> LD init/built-in.o
> >> arch/x86/built-in.o: In function `setup_arch':
> >> (.init.text+0x359e): undefined reference to `early_pci_allowed'
> >> arch/x86/built-in.o: In function `setup_arch':
> >> (.init.text+0x35b2): undefined reference to `read_pci_config_16'
> >> arch/x86/built-in.o: In function `setup_arch':
> >> (.init.text+0x35cb): undefined reference to `read_pci_config_16'
> >> make[1]: *** [vmlinux] Fehler 1
> >> make: *** [sub-make] Fehler 2
> >>
> >> I'm building a Xen domU kernel without modules (one big binary of
> >> everything).
> >
> >
> > You had to revert _what_?
>
> The patch from 3.7.3 to 3.7.4.
> Sorry for the confusion.
>
> The problem seems to be caused by this:
> > http://www.kernel.org/diff/diffview.cgi?file=%2Fpub%2Flinux%2Fkernel%2Fv3.0%2Fincr%2Fpatch-3.7.3-4.bz2;z=8
The whole patch?
Any chance you can use 'git bisect' on the 3.7.4 tree, marking 3.7.3
good, so we can find the patch that caused the problem and revert it?
thanks,
greg k-h
prev parent reply other threads:[~2013-01-24 18:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 19:54 Linux 3.7.4 Greg KH
2013-01-21 19:54 ` Greg KH
[not found] ` <kdq4sd$g3c$1@ger.gmane.org>
2013-01-24 2:24 ` Greg KH
2013-01-24 2:37 ` Sven Köhler
2013-01-24 18:17 ` Greg KH [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=20130124181726.GD12106@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=sven.koehler@gmail.com \
/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