From: "Sachin P. Sant" <sachinp@in.ibm.com>
To: michael@ellerman.id.au
Cc: linuxppc-dev@ozlabs.org, Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org
Subject: Re: [Powerpc] Next March 5 build failure: platform/pseries/msi.o
Date: Thu, 05 Mar 2009 22:23:29 +0530 [thread overview]
Message-ID: <49B00389.7050407@in.ibm.com> (raw)
In-Reply-To: <1236262014.8325.10.camel@localhost>
Michael Ellerman wrote:
> Dang it, that's my fault. Thanks for catching it Sachin.
>
> I assumed pseries always enabled EEH, but I see now you can disable it
> if you have EMBEDDED set (which your config does).
>
> It's a bit yucky making the MSI code depend on EEH, but the only other
> option would be to pull half the EEH code out - so I guess that's what
> I'll do.
>
> Does this patch fix it?
Thanks for the patch Michael. It fixes the build break.
Regards
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
WARNING: multiple messages have this Message-ID (diff)
From: "Sachin P. Sant" <sachinp@in.ibm.com>
To: michael@ellerman.id.au
Cc: linuxppc-dev@ozlabs.org, linux-next@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [Powerpc] Next March 5 build failure: platform/pseries/msi.o
Date: Thu, 05 Mar 2009 22:23:29 +0530 [thread overview]
Message-ID: <49B00389.7050407@in.ibm.com> (raw)
In-Reply-To: <1236262014.8325.10.camel@localhost>
Michael Ellerman wrote:
> Dang it, that's my fault. Thanks for catching it Sachin.
>
> I assumed pseries always enabled EEH, but I see now you can disable it
> if you have EMBEDDED set (which your config does).
>
> It's a bit yucky making the MSI code depend on EEH, but the only other
> option would be to pull half the EEH code out - so I guess that's what
> I'll do.
>
> Does this patch fix it?
Thanks for the patch Michael. It fixes the build break.
Regards
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
next prev parent reply other threads:[~2009-03-05 16:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-05 8:50 linux-next: Tree for March 5 Stephen Rothwell
2009-03-05 11:36 ` [Powerpc] Next March 5 build failure: platform/pseries/msi.o Sachin P. Sant
2009-03-05 14:06 ` Michael Ellerman
2009-03-05 14:06 ` Michael Ellerman
2009-03-05 16:53 ` Sachin P. Sant [this message]
2009-03-05 16:53 ` Sachin P. Sant
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=49B00389.7050407@in.ibm.com \
--to=sachinp@in.ibm.com \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=sfr@canb.auug.org.au \
/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.