All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Roger Luethi <rl@hellgate.ch>
Cc: Andrew Morton <akpm@digeo.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][2.5][Trivial] VIA Rhine Kconfig entry
Date: Sat, 07 Dec 2002 22:15:42 -0500	[thread overview]
Message-ID: <3DF2B95E.5060706@pobox.com> (raw)
In-Reply-To: <20021208003456.GA12234@k3.hellgate.ch>

Roger Luethi wrote:
> at it. Just barely resisted the temptation to make VIA Rhine conflict with
> IO-APIC -- that seems to emerge as a fatal combo.


Patch looks ok to me, I'll queue it.

I agree about IO-APIC -- though I also think the reports that replacing 
via-rhine with linuxfet, and changing nothing else, helps the situation.

It might be something cosmetic like silly dev->tx_timeout handling, or 
it might be something useful like a chip-specific patch [often happens 
with on-mobo chips] or even a north/south-bridge-specific fixup.

	Jeff




  reply	other threads:[~2002-12-08  3:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-08  0:34 [PATCH][2.5][Trivial] VIA Rhine Kconfig entry Roger Luethi
2002-12-08  3:15 ` Jeff Garzik [this message]
2002-12-10 13:28   ` Roger Luethi
2002-12-10 19:19     ` Steve Brueggeman
2002-12-10 20:52       ` Alan Cox

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=3DF2B95E.5060706@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rl@hellgate.ch \
    /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.