From: Michael Ellerman <michael@ellerman.id.au>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Make #include <sysdev/foo.h> work for 64-bit powerpc
Date: Wed, 02 Apr 2008 12:55:54 +1100 [thread overview]
Message-ID: <1207101354.7349.0.camel@concordia.ozlabs.ibm.com> (raw)
In-Reply-To: <0A4216BD-1505-46DE-B08E-23E9B7E51AD2@kernel.crashing.org>
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
On Tue, 2008-04-01 at 08:18 -0500, Kumar Gala wrote:
> On Apr 1, 2008, at 1:54 AM, Stephen Rothwell wrote:
> > Hi Michael,
> >
> > On Tue, 1 Apr 2008 17:39:11 +1100 (EST) Michael Ellerman <michael@ellerman.id.au
> > > wrote:
> >>
> >> We currently have inconsistent settings between 32 & 64-bit which
> >> means
> >> 32-bit code can #include <sysdev/foo.h> but 64-bit code can't.
> >
> > Kumar sent a very similar (if not identical) patch earlier today.
>
> I actually sent it several days ago, but reposted as part of the
> series of work I was doing. ;)
OK, I missed it. I'm not fussed who's goes in, I just needed it for some
other work.
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2008-04-02 1:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 6:39 [PATCH] Make #include <sysdev/foo.h> work for 64-bit powerpc Michael Ellerman
2008-04-01 6:54 ` Stephen Rothwell
2008-04-01 13:18 ` Kumar Gala
2008-04-02 1:55 ` Michael Ellerman [this message]
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=1207101354.7349.0.camel@concordia.ozlabs.ibm.com \
--to=michael@ellerman.id.au \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox