public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chuck Ebbert <cebbert@redhat.com>
To: Leroy van Logchem <leroy.vanlogchem@wldelft.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y [Fix CONFIG_COMPAT_VDSO] <- Bad
Date: Thu, 15 Mar 2007 11:31:00 -0400	[thread overview]
Message-ID: <45F966B4.8070607@redhat.com> (raw)
In-Reply-To: <loom.20070314T184515-284@post.gmane.org>

Leroy van Logchem wrote:
> 
> Bisecting went well, after 13 compiles this commit was found:
> 
> a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f is first bad commit
> commit a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f
> Author: Roland McGrath <roland@redhat.com>
> Date:   Fri Jan 26 00:56:46 2007 -0800
> 
>     [PATCH] Fix CONFIG_COMPAT_VDSO
>     

So you do have CONFIG_COMPAT_VDSO in your config, then?


  parent reply	other threads:[~2007-03-15 15:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200703141013.l2EADP6c027144@fire-2.osdl.org>
2007-03-14 12:17 ` [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y Andrew Morton
2007-03-14 11:25   ` Randy.Dunlap
2007-03-14 11:30   ` Michal Piotrowski
2007-03-14 12:16     ` Leroy van Logchem
2007-03-14 17:52       ` [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y [Fix CONFIG_COMPAT_VDSO] <- Bad Leroy van Logchem
2007-03-15  1:01         ` Andrew Morton
2007-03-15  0:13           ` Andi Kleen
2007-03-15 14:12             ` [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y [Fix CONFIG_COMPAT_VDSO] <- Bad? Leroy van Logchem
2007-03-16  7:41               ` Nilshar
2007-03-15 15:31         ` Chuck Ebbert [this message]
2007-03-15 15:49           ` [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y [Fix CONFIG_COMPAT_VDSO] <- Bad Leroy van Logchem
2007-03-15 10:02       ` [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y Nilshar

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=45F966B4.8070607@redhat.com \
    --to=cebbert@redhat.com \
    --cc=leroy.vanlogchem@wldelft.nl \
    --cc=linux-kernel@vger.kernel.org \
    /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