From: Michael Ellerman <mpe@ellerman•id.au>
To: Cyril Bur <cyrilbur@gmail•com>, Jack Miller <jack@codezen•org>,
linuxppc-dev@lists•ozlabs.org
Cc: stewart@linux•vnet.ibm.com, jk@ozlabs•org
Subject: Re: [PATCH v2] powernv: Simplify searching for compatible device nodes
Date: Thu, 04 Aug 2016 18:39:24 +1000 [thread overview]
Message-ID: <87k2fxexmr.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20160804172727.55e81056@camb691>
Cyril Bur <cyrilbur@gmail•com> writes:
> On Wed, 3 Aug 2016 12:18:00 -0500
> Jack Miller <jack@codezen•org> wrote:
>
>> (rebased on powerpc/next)
>>
>> This condenses the opal node searching into a single function that finds
>> all compatible nodes, instead of just searching the ibm,opal children,
>> for ipmi, flash, and prd similar to how opal-i2c nodes are found.
>>
>> Signed-off-by: Jack Miller <jack@codezen•org>
>
> Using a version of the related skiboot patch that may not be the final one:
> Tested-by: Cyril Bur <cyrilbur@gmail•com>
Thanks. The part I'm still not clear on is *why* we're moving them in
skiboot?
cheers
next prev parent reply other threads:[~2016-08-04 8:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-01 20:50 [PATCH] powernv: Search for new flash DT node location Jack Miller
2016-08-01 21:04 ` Jack Miller
2016-08-03 7:16 ` Michael Ellerman
2016-08-03 16:44 ` Jack Miller
2016-08-03 16:44 ` [PATCH] powernv: Simplify searching for compatible device nodes Jack Miller
2016-08-03 17:18 ` [PATCH v2] " Jack Miller
2016-08-04 7:27 ` Cyril Bur
2016-08-04 8:39 ` Michael Ellerman [this message]
2016-08-04 16:03 ` Jack Miller
2016-08-04 3:28 ` [PATCH] powernv: Search for new flash DT node location Michael Ellerman
2016-09-27 4:44 ` Stewart Smith
-- strict thread matches above, loose matches on Subject: below --
2016-08-11 0:32 [PATCH v2] powernv: Simplify searching for compatible device nodes Jack Miller
2016-10-19 5:58 ` Cyril Bur
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=87k2fxexmr.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman$(echo .)id.au \
--cc=cyrilbur@gmail$(echo .)com \
--cc=jack@codezen$(echo .)org \
--cc=jk@ozlabs$(echo .)org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=stewart@linux$(echo .)vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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