From: Olaf Hering <olh@suse.de>
To: Tom Rini <trini@kernel.crashing.org>, linuxppc-dev@lists.linuxppc.org
Subject: Re: linuxppc-2.5 CONFIG_BOOT_LOAD undefined
Date: Sat, 16 Aug 2003 13:41:41 +0200 [thread overview]
Message-ID: <20030816114141.GA7095@suse.de> (raw)
In-Reply-To: <20030816074947.GA4087@mars.ravnborg.org>
On Sat, Aug 16, Sam Ravnborg wrote:
> On Thu, Aug 14, 2003 at 11:02:57PM +0200, Sam Ravnborg wrote:
> >
> > I will try to fix it during the weekend.
> Olaf - care to try the following patch.
> It is on top of linus's tree, but I expect it to apply
> to your ppc tree as well.
Yes, works for me [TM].
--
USB is for mice, FireWire is for men!
sUse lINUX ag, nÜRNBERG
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-08-16 11:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-13 7:51 linuxppc-2.5 CONFIG_BOOT_LOAD undefined Olaf Hering
2003-08-13 23:35 ` Tom Rini
2003-08-14 10:39 ` Olaf Hering
2003-08-14 16:05 ` Tom Rini
2003-08-14 16:45 ` Olaf Hering
2003-08-14 16:54 ` Tom Rini
2003-08-14 17:44 ` Olaf Hering
2003-08-14 18:43 ` Tom Rini
2003-08-14 19:31 ` Sam Ravnborg
2003-08-14 19:34 ` Olaf Hering
2003-08-14 21:02 ` Sam Ravnborg
2003-08-16 7:49 ` Sam Ravnborg
2003-08-16 11:41 ` Olaf Hering [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=20030816114141.GA7095@suse.de \
--to=olh@suse.de \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=trini@kernel.crashing.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).