From: David Miller <davem@davemloft.net>
To: mchan@broadcom.com
Cc: mcarlson@broadcom.com, netdev@vger.kernel.org, andy@greyhouse.net
Subject: Re: [PATCH 1/1] tg3: Avoid Send BD corruption
Date: Thu, 11 Sep 2008 16:30:20 -0700 (PDT) [thread overview]
Message-ID: <20080911.163020.209586511.davem@davemloft.net> (raw)
In-Reply-To: <1221175168.12785.40.camel@HP1>
From: "Michael Chan" <mchan@broadcom.com>
Date: Thu, 11 Sep 2008 16:19:28 -0700
> OK, we'll resubmit this for net-next then. But I still think this one
> should qualify. We do internal testing to find as many problems as
> possible so that real users don't see too many of them.
If driver authors can do these kinds of things to their heart's
content, and then submit lots of patches fixing all the bugs they
find, where are we able to draw the line?
That's the problem. And right now my (and Linus's) solution is to push
back and say no unless it meets strict criteria.
prev parent reply other threads:[~2008-09-11 23:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 5:12 [PATCH 1/1] tg3: Avoid Send BD corruption Matt Carlson
2008-09-11 5:46 ` David Miller
2008-09-11 16:59 ` Matt Carlson
2008-09-11 21:51 ` David Miller
2008-09-11 22:55 ` Michael Chan
2008-09-11 23:01 ` David Miller
2008-09-11 23:19 ` Michael Chan
2008-09-11 23:30 ` David Miller [this message]
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=20080911.163020.209586511.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andy@greyhouse.net \
--cc=mcarlson@broadcom.com \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.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).