From: Tom Rini <trini@kernel.crashing.org>
To: Dan Malek <dan@embeddededge.com>
Cc: Embedded PPC Linux list <linuxppc-embedded@ozlabs.org>
Subject: Re: [PATCH] first in a series to enhance microcode patches
Date: Tue, 5 Oct 2004 12:29:50 -0700 [thread overview]
Message-ID: <20041005192950.GL32692@smtp.west.cox.net> (raw)
In-Reply-To: <A337CA12-1703-11D9-B4FB-003065F9B7DC@embeddededge.com>
On Tue, Oct 05, 2004 at 03:20:37PM -0400, Dan Malek wrote:
>
> On Oct 5, 2004, at 12:32 PM, Robert P. J. Day wrote:
>
> > (after a short discussion with tom rini, we're going to ignore any
> >previous patch submissions of mine WRT microcode patches and start
> >fresh. first trivial patch, just to start things off.)
>
> No, send a whole patch that _does_ something. Let's see all of these
> changes at once. By itself, this patch is useless and doesn't add any
> features, it just wastes our time discussing it.
A series of inter-dependant patches might be better, but I like small,
easy to understand patches.
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2004-10-05 19:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 16:32 [PATCH] first in a series to enhance microcode patches Robert P. J. Day
2004-10-05 19:20 ` Dan Malek
2004-10-05 19:29 ` Tom Rini [this message]
2004-10-05 20:00 ` Robert P. J. Day
2004-10-05 20:53 ` Tom Rini
2004-10-05 19:52 ` Robert P. J. Day
2004-10-05 20:20 ` Wolfgang Denk
2004-10-06 13:30 ` Robert P. J. Day
2004-10-06 14:05 ` Mark Chambers
2004-10-06 14:01 ` Robert P. J. Day
-- strict thread matches above, loose matches on Subject: below --
2004-10-05 17:32 Robert P. J. Day
2004-10-07 15:38 ` Tom Rini
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=20041005192950.GL32692@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=dan@embeddededge.com \
--cc=linuxppc-embedded@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).