From: Grant Likely <grant.likely@secretlab.ca>
To: benh@kernel.crashing.org, galak@kernel.crashing.org,
sfr@canb.auug.org.au,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: [PATCH V2 0/3] Make 64-bit PCI device tree scanning code common
Date: Wed, 26 Aug 2009 00:07:44 -0600 [thread overview]
Message-ID: <fa686aa40908252307j5fe05db1g8defc09e6eed988b@mail.gmail.com> (raw)
In-Reply-To: <20090825162314.10936.11028.stgit@localhost.localdomain>
Hi guys
Here's v2 of the PCI device tree scanning code. =A0This is tested and
working on 32bit. =A0It needs to be tested on 64 bit, but there shouldn't
be any behavioural changes. =A0It's mostly just a code move with a little
bit of fixups to merge code. =A0I'd like to see this go into .32 when the
merge window opens.
Changes in v2:
- Move scanning code into its own file: pci_of_scan.c
On Thu, Aug 20, 2009 at 11:30 PM, Grant Likely<grant.likely@secretlab.ca> w=
rote:
> Ben and Kumar,
>
> Compile tested only. =A0I haven't even tried to boot this on real
> hardware, but I'm posting so that you guys can see what I'm up to.
> Basically, I want access to the device tree scanning in ppc32 land,
> and these patches start to get me there. =A0Please take a look and
> comment. =A0Tomorrow I'll actually try running this stuff and debugging
> the details.
>
--
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
--=20
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next parent reply other threads:[~2009-08-26 6:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090825162314.10936.11028.stgit@localhost.localdomain>
2009-08-26 6:07 ` Grant Likely [this message]
2009-08-26 6:09 ` [PATCH V2 0/3] Make 64-bit PCI device tree scanning code common Grant Likely
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=fa686aa40908252307j5fe05db1g8defc09e6eed988b@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=benh@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@lists.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