From: Ingo Molnar <mingo@elte.hu>
To: Dave Jones <davej@redhat.com>,
Tarkan Erimer <tarkan.erimer@turknet.net.tr>,
linux-kernel@vger.kernel.org
Subject: Re: Linux-2.6.29-git6 Compile Error
Date: Sat, 4 Apr 2009 23:24:50 +0200 [thread overview]
Message-ID: <20090404212450.GA14729@elte.hu> (raw)
In-Reply-To: <20090403175355.GB26888@redhat.com>
* Dave Jones <davej@redhat.com> wrote:
> On Fri, Apr 03, 2009 at 07:47:01PM +0200, Ingo Molnar wrote:
> >
> > * Dave Jones <davej@redhat.com> wrote:
> >
> > > On Mon, Mar 30, 2009 at 04:34:38PM +0200, Ingo Molnar wrote:
> > > >
> > > > (Cc: added)
> > >
> > > See 199785eac892a1fa1b71cc22bec58e8b156d9311
> > > Steven picked up in this build failure _months_ ago in -next,
> > > which caused me to regenerate the cpufreq tree so that the build failure
> > > wouldn't get introduced to mainline.
> > >
> > > Then the x86-merge comes along, and steamrollers over it.
> >
> > hmmm ... there certainly was no build failure observable here.
> > Which commit caused the problem? 199785eac8 went in via your
> > tree, not the x86 tree.
>
> The commits that moved the include file around reverted the
> changes from 199785eac8.
ah. That was indeed my bad - sorry about that. Should we have
applied that fix to the x86 tree or did it only make sense after
the merge?
Ingo
next prev parent reply other threads:[~2009-04-04 21:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-30 14:14 Linux-2.6.29-git6 Compile Error Tarkan Erimer
2009-03-30 14:34 ` Ingo Molnar
2009-03-30 16:47 ` Dave Jones
2009-04-03 17:47 ` Ingo Molnar
2009-04-03 17:53 ` Dave Jones
2009-04-04 21:24 ` Ingo Molnar [this message]
[not found] ` <bb33bcf20903300748i66eec692hf9ba571758ebc29@mail.gmail.com>
2009-03-30 14:59 ` Tarkan Erimer
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=20090404212450.GA14729@elte.hu \
--to=mingo@elte.hu \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tarkan.erimer@turknet.net.tr \
/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.