From: Tom Rini <trini@kernel.crashing.org>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Embedded PPC Linux list <linuxppc-embedded@ozlabs.org>
Subject: Re: [PATCH] 2.6.9(?) kernel, replacing ucode patch infrastructure
Date: Thu, 7 Oct 2004 08:45:57 -0700 [thread overview]
Message-ID: <20041007154557.GF14773@smtp.west.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.60.0410060908520.8324@dell.enoriver.com>
On Wed, Oct 06, 2004 at 09:15:56AM -0400, Robert P. J. Day wrote:
>
> ok, one more time, here's a patch that should apply cleanly to the
> latest bk repo for linuxppc-2.5. the purpose is to create a cleaner
> and more extensible microcode patch infrastructure, so that all you
> need to do is *select* the 8xx-relevant patch you want from the config
> menu under "MPC8xx" options.
This doesn't apply cleanly, even if I tell patch to ignore whitespace
changes. Please re-generate, thanks.
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2004-10-07 15:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-06 13:15 [PATCH] 2.6.9(?) kernel, replacing ucode patch infrastructure Robert P. J. Day
2004-10-07 15:45 ` Tom Rini [this message]
2004-10-07 16:17 ` Robert P. J. Day
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=20041007154557.GF14773@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=rpjday@mindspring.com \
/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).