mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Greg KH <gregkh@suse.de>
Cc: pbadari@us.ibm.com, torvalds@osdl.org,
	linux-kernel@vger.kernel.org, kamezawa.hiroyu@jp.fujitsu.com
Subject: Re: 2.6.17-git14 compile failure & fix
Date: Thu, 29 Jun 2006 11:29:52 -0700	[thread overview]
Message-ID: <20060629112952.c7231034.akpm@osdl.org> (raw)
In-Reply-To: <20060629172016.GA23736@suse.de>

On Thu, 29 Jun 2006 10:20:16 -0700
Greg KH <gregkh@suse.de> wrote:

> 
> On Thu, Jun 29, 2006 at 10:05:56AM -0700, Badari Pulavarty wrote:
> > Hi,
> > 
> > I get "unknown definition" compile failure while compiling 2.6.17-git14
> > with CONFIG_MEMORY_HOTPLUG. (kernel/resource.c line: 243) -
> > due to recent changes to it.
> > 
> > Here is the patch to fix it. I can't take credit for the patch, since its
> > part of GregKH resource_t  patches :)
> 
> Ick, yeah, that's a fix,

Oh crap, sorry, patch skew.  That never turned up in my cross-compiling :(

(It's *really hard* to turn on CONFIG_MEMORY_HOTPLUG.  Even ia64
allmodconfig won't do it).

> but the "real" fix would be for Linus to pull
> from my PCI tree which has all of the resource changes in it already
> (I sent a request to do so a few days ago...)
> 
> Linus, here's the summary again below if you want to pull.  When you
> merge, there might be some conflicts you have to handle, but hey, you
> can test out your new git merge code :)

Yes, please let's get this in.

  reply	other threads:[~2006-06-29 18:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-29 17:05 Badari Pulavarty
2006-06-29 17:20 ` Greg KH
2006-06-29 18:29   ` Andrew Morton [this message]
2006-06-29 18:36     ` Linus Torvalds
2006-06-29 18:56     ` Badari Pulavarty

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=20060629112952.c7231034.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=gregkh@suse.de \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbadari@us.ibm.com \
    --cc=torvalds@osdl.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

all inboxes | Powered by JetHome®