public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Roland Dreier <rdreier@cisco•com>
To: "Ruslan V. Sushko" <rsushko@ru•mvista.com>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: [PATCH 2/5] ppc32: verbose error checking for Yucca PCIE initialization
Date: Tue, 06 Dec 2005 21:17:42 -0800	[thread overview]
Message-ID: <ada3bl5pjt5.fsf@cisco.com> (raw)
In-Reply-To: <1133873391.16347.42.camel@mephisto.spb.rtsoft.ru> (Ruslan V. Sushko's message of "Tue, 06 Dec 2005 15:49:51 +0300")

    Ruslan> I haven't saw any error but this is potential issue
    Ruslan> because this flag asserts only then PCI Express port
    Ruslan> initialization is completed. I guess the initialization
    Ruslan> sequences assumes time using. Therefore the error may
    Ruslan> appears in future revision of the boards if Core clock
    Ruslan> will grow up.  Nevertheless I do not know the time which
    Ruslan> is necessary for completeness, so I add this just to be
    Ruslan> safe.

Hmm, I guess this is OK.  Matt, go ahead and apply this.

 - R.

      reply	other threads:[~2005-12-07  5:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-06 12:49 [PATCH 2/5] ppc32: verbose error checking for Yucca PCIE initialization Ruslan V. Sushko
2005-12-07  5:17 ` Roland Dreier [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=ada3bl5pjt5.fsf@cisco.com \
    --to=rdreier@cisco$(echo .)com \
    --cc=linuxppc-embedded@ozlabs$(echo .)org \
    --cc=rsushko@ru$(echo .)mvista.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