All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Auke Kok <sofar@lunar-linux.org>,
	linux-kernel@vger.kernel.org, vortex@scyld.com
Subject: Re: [PATCH][2.4.28-pre3] 3c59x builtin NIC on Asus Pundit-R
Date: Wed, 1 Dec 2004 15:23:18 -0200	[thread overview]
Message-ID: <20041201172318.GK2250@dmt.cyclades> (raw)
In-Reply-To: <20041201131127.208e15b6.akpm@osdl.org>

On Wed, Dec 01, 2004 at 01:11:27PM -0800, Andrew Morton wrote:
> Auke Kok <sofar@lunar-linux.org> wrote:
> >
> > 
> > This message is a confirmation on the thread by:
> > 
> > From: Andreas Haumer
> > Date: Tue Sep 21 2004 - 04:16:52 EST
> > Subject: [PATCH][2.4.28-pre3] 3c59x builtin NIC on Asus Pundit-R
> > 
> > I have 24 boxes with the same hardware and all require the patch 
> > attached to Andreas' e-mail to function. After abusing one of them for 2 
> > days continuously the nic hasn't shown a single flaw so far ;^)
> > 
> > I thus would like to conclude that this patch is a valid and worthfull 
> > addition to the 2.4.28+ kernels, as it applies cleanly to 2.4.28-final.
> > 
> > Auke kok
> > 
> > 
> > PS URL to the patch: 
> > http://www.ussg.iu.edu/hypermail/linux/kernel/0409.2/1215/013-3com_ati_radeon.patch
> 
> That patch should of course be merged.  Please email a copy to Marcelo.

This has been merged together with 3c59x's v2.6 sync in 2.4.29-pre1.
Can you give that a shot Auke?

  reply	other threads:[~2004-12-01 23:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-01 20:15 [PATCH][2.4.28-pre3] 3c59x builtin NIC on Asus Pundit-R Auke Kok
2004-12-01 21:11 ` Andrew Morton
2004-12-01 17:23   ` Marcelo Tosatti [this message]
2004-12-02 11:20     ` Auke Kok
  -- strict thread matches above, loose matches on Subject: below --
2004-09-21  9:14 Andreas Haumer

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=20041201172318.GK2250@dmt.cyclades \
    --to=marcelo.tosatti@cyclades.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sofar@lunar-linux.org \
    --cc=vortex@scyld.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.