From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Martin Dalecki <dalecki@evision-ventures.com>
Cc: Luigi Genoni <kernel@Expansa.sns.it>,
linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: cleanup for i810 chipset for 2.5.5-pre1. Second...
Date: Fri, 15 Feb 2002 02:55:06 -0500 [thread overview]
Message-ID: <3C6CBEDA.DB6BDA50@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0202141819080.30210-100000@Expansa.sns.it> <3C6CB8DD.9040602@evision-ventures.com>
Martin Dalecki wrote:
>
> Luigi Genoni wrote:
>
> >Well, my mailer did some bad things with tabs, spaces and so on...
> >What can I say, I hate when it happens, I hope this time is the good one.
> >
>
> Well better take this, it should make even DM and JG as well as other
> "portability" fanatics happy ;-).
> And as a bonus I'm just adding a fixing note to the documentation, which
> by the way is
> no longer accurate.
Well, I've mentioned this at least three times, Pete Zaitcev has a patch
which fixes i810_audio properly -- and he even posted it to lkml less
than 24 hours ago. Subject "Re: 2.5.5-pre1 and i810_audio.c",
message-id <200202141842.g1EIgcR12566@devserv.devel.redhat.com>
Further, Alan Cox pointed out that the i810_audio workalike chipsets
exist on Alpha, so your solution is still non-portable specifically for
case where portability is needed.
Jeff
--
Jeff Garzik | "I went through my candy like hot oatmeal
Building 1024 | through an internally-buttered weasel."
MandrakeSoft | - goats.com
next prev parent reply other threads:[~2002-02-15 7:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-14 17:26 cleanup for i810 chipset for 2.5.5-pre1. Second Luigi Genoni
2002-02-15 7:29 ` Martin Dalecki
2002-02-15 7:55 ` Jeff Garzik [this message]
[not found] ` <mailman.1013758321.20800.linux-kernel2news@redhat.com>
2002-02-15 19:33 ` Pete Zaitcev
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=3C6CBEDA.DB6BDA50@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=dalecki@evision-ventures.com \
--cc=kernel@Expansa.sns.it \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 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.