From: Jeff Garzik <jgarzik@pobox.com>
To: Clint Adams <schizo@debian.org>
Cc: "Luis R. Rodriguez" <mcgrof@ruslug.rutgers.edu>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
prism54-devel@prism54.org, debian-kernel@lists.debian.org
Subject: Re: Re: [PATCH 0/14] prism54: bring up to sync with prism54.org cvs rep
Date: Thu, 27 May 2004 14:40:57 -0400 [thread overview]
Message-ID: <40B63639.6080705@pobox.com> (raw)
In-Reply-To: <20040527182531.GA8942@scowler.net>
Clint Adams wrote:
>>>[PATCH 8/14 linux-2.6.7-rc1] prism54: Fix prism54.org bugs 39, 73
>
>
>>I'm considering rejecting the entire series because of this obfuscation
>>of changes, and getting you to resend with the whitespace crapola
>>separated out.
>
>
> Please at least apply the changes in the "8/14" patch, because without
> them the driver is unusable on big-endian architectures.
The entire patch series was dropped.
Luis, you, or somebody should create a new patch series with just the
critical fixes, NO WHITESPACE/FORMATTING CHANGES mixed in, and send
those first.
Jeff
next prev parent reply other threads:[~2004-05-27 18:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-24 8:30 [PATCH 0/14] prism54: bring up to sync with prism54.org cvs rep Luis R. Rodriguez
2004-05-24 8:57 ` Luis R. Rodriguez
2004-05-27 18:10 ` Jeff Garzik
2004-05-27 19:27 ` Marcelo Tosatti
2004-05-27 19:32 ` Jeff Garzik
2004-05-27 19:45 ` Luis R. Rodriguez
2004-05-27 19:56 ` Jeff Garzik
2004-05-27 20:04 ` Luis R. Rodriguez
2004-05-27 18:19 ` Jeff Garzik
2004-05-27 18:25 ` Clint Adams
2004-05-27 18:40 ` Jeff Garzik [this message]
2004-05-27 19:05 ` [Prism54-devel] " Andrew Morton
2004-05-27 19:24 ` Jeff Garzik
2004-05-27 18:39 ` Jeff Garzik
[not found] <5.1.0.14.2.20040528090459.00ae3d18@pop.t-online.de>
2004-05-29 8:38 ` Luis R. Rodriguez
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=40B63639.6080705@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=debian-kernel@lists.debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@ruslug.rutgers.edu \
--cc=netdev@oss.sgi.com \
--cc=prism54-devel@prism54.org \
--cc=schizo@debian.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).