From: bill4carson <bill4carson@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] Copy machine descriptor after probe succeed
Date: Wed, 21 Dec 2011 10:15:50 +0800 [thread overview]
Message-ID: <4EF14156.3040509@gmail.com> (raw)
In-Reply-To: <20111220211751.7dcff65ecfb1c5eaf022070d@canb.auug.org.au>
On 2011年12月20日 18:17, Stephen Rothwell wrote:
> Hi Bill,
>
> On Tue, 20 Dec 2011 17:08:47 +0800 bill4carson@gmail.com wrote:
>> From: Bill Carson<bill4carson@gmail.com>
>>
>> It make more sense to copy machine descriptor AFTER machine probe return
>> succeed.
> Some of the platform's probe routines modify the ppc_md structure and so
> assume that it is has been popluated before the probe routine is called.
>
I didn't see the whole picture before :(
thanks for your point.
--
I am a slow learner
but I will keep trying to fight for my dreams!
--bill
prev parent reply other threads:[~2011-12-21 2:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-20 9:08 [PATCH-v1]Copy machine descriptor after probe succeed bill4carson
2011-12-20 9:08 ` [PATCH] Copy " bill4carson
2011-12-20 10:17 ` Stephen Rothwell
2011-12-21 2:15 ` bill4carson [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=4EF14156.3040509@gmail.com \
--to=bill4carson@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).