From: Stephen Williams <steve@icarus.com>
To: Andrei Konovalov <akonovalov@ru.mvista.com>,
linuxppc-embedded@lists.linuxppc.org
Subject: Patch for SystemACE without CONFIG_XILINX_OCP
Date: Mon, 26 Jul 2004 12:16:17 -0700 [thread overview]
Message-ID: <41055881.6000707@icarus.com> (raw)
hI,
I passed around the attached patch in hopes that it could be
integrated into the linuxppc-2.4 bitkeeper tree, assuming that
is the best place to maintain linux 2.4 for PPC. But I don't
see it showing up in the repository.
Actually, I noticed that there were no changes to the tree
in a little while. Is everybody off working on 2.6? Should
I be there too?
- --
Steve Williams "The woods are lovely, dark and deep.
steve at icarus.com But I have promises to keep,
http://www.icarus.com and lines to code before I sleep,
http://www.picturel.com And lines to code before I sleep."
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2004-07-26 19:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 19:16 Stephen Williams [this message]
2004-07-26 20:04 ` Patch for SystemACE without CONFIG_XILINX_OCP Stephen Williams
2004-07-28 16:56 ` Scott Anderson
2004-07-29 21:56 ` Stephen Williams
2004-07-29 23:38 ` new home for this list? Tom Curran
2004-07-30 1:47 ` Dave Wolfe
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=41055881.6000707@icarus.com \
--to=steve@icarus.com \
--cc=akonovalov@ru.mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.