From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Jon Loeliger" <jdl@jdl.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [RFC PATCH 0/3]: Add StorCenter port to arch/powerpc
Date: Mon, 7 Jan 2008 12:34:02 -0700 [thread overview]
Message-ID: <fa686aa40801071134t7963a233yb40984e84170d0b7@mail.gmail.com> (raw)
In-Reply-To: <E1JBwAx-0006Il-CE@jdl.com>
On 1/7/08, Jon Loeliger <jdl@jdl.com> wrote:
> Specifically, it's not quite working yet, and for lack of
> actually getting serial output, we're having some difficulty
> still. I post it here in a desperate attempt to let some
> eagle-eyed person point out my obvious "D'oh" problem.
Can you access __log_buf in any way at all?
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next prev parent reply other threads:[~2008-01-07 19:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-07 17:54 [RFC PATCH 0/3]: Add StorCenter port to arch/powerpc Jon Loeliger
2008-01-07 19:34 ` Grant Likely [this message]
2008-01-07 20:14 ` Jon Loeliger
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=fa686aa40801071134t7963a233yb40984e84170d0b7@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=jdl@jdl.com \
--cc=linuxppc-dev@ozlabs.org \
/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).