From: Paul Mackerras <paulus@samba.org>
To: Greg KH <greg@kroah.com>
Cc: linuxppc64-dev@ozlabs.org, torvalds@osdl.org,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, johnrose@austin.ibm.com
Subject: Re: fix build breakage in eeh.c in 2.6.16-rc5-git5
Date: Thu, 2 Mar 2006 08:54:56 +1100 [thread overview]
Message-ID: <17414.6192.426294.502401@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20060301214600.GA17702@kroah.com>
Greg KH writes:
> This patch should fixe a problem with eeh_add_device_late() not being
> defined in the ppc64 build process, causing the build to break.
John Rose just sent a patch making eeh_add_device_late static and
moving it to be defined before it is called in
arch/powerpc/platforms/pseries/eeh.c.
Since he maintains this stuff, I'm more inclined to take his patch.
Paul.
next prev parent reply other threads:[~2006-03-01 21:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 21:46 Greg KH
2006-03-01 21:54 ` Paul Mackerras [this message]
2006-03-01 22:03 ` Greg KH
2006-03-01 22:15 ` Greg KH
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=17414.6192.426294.502401@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=johnrose@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@ozlabs.org \
--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®