From: Ron Madrid <ron_madrid@sbcglobal.net>
To: michael@ellerman.id.au
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Bootlog bug?
Date: Mon, 30 Mar 2009 14:11:54 -0700 (PDT) [thread overview]
Message-ID: <21841.75975.qm@web83504.mail.sp1.yahoo.com> (raw)
In-Reply-To: <1238107887.15460.3.camel@localhost>
--- On Thu, 3/26/09, Michael Ellerman <michael@ellerman.id.au> wrote:
> From: Michael Ellerman <michael@ellerman.id.au>
> Subject: Re: Bootlog bug?
> To: ron_madrid@sbcglobal.net
> Cc: linuxppc-dev@ozlabs.org
> Date: Thursday, March 26, 2009, 3:51 PM
> On Thu, 2009-03-26 at 11:25 -0700, Ron Madrid wrote:
> > I have a little problem with my boot messages.
> I'm not sure what this
> > is, but does anyone have any ideas as to what it could
> be or what
> > further information I could give to help track this
> down. As of now
> > this is not manifesting itself, but I don't know
> what it might do.
>
> You have ended up with a duplicate device, or duplicate
> device _name_,
> somehow.
Thank you. I found my duplicate device!
Ron
prev parent reply other threads:[~2009-03-30 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 18:25 Bootlog bug? Ron Madrid
2009-03-26 22:51 ` Michael Ellerman
2009-03-30 21:11 ` Ron Madrid [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=21841.75975.qm@web83504.mail.sp1.yahoo.com \
--to=ron_madrid@sbcglobal.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.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).