From: David Miller <davem@davemloft.net>
To: aabdulla@nvidia.com
Cc: manfred@colorfullife.com, akpm@osdl.org, netdev@vger.kernel.org
Subject: Re: [PATCH] forcedeth: updated phy errata
Date: Fri, 04 Sep 2009 15:00:15 -0700 (PDT) [thread overview]
Message-ID: <20090904.150015.247320928.davem@davemloft.net> (raw)
In-Reply-To: <4AA11CE7.7050400@nvidia.com>
From: Ayaz Abdulla <aabdulla@nvidia.com>
Date: Fri, 04 Sep 2009 09:57:59 -0400
> Unfortunately, the phy vendors don't want us exposing the meaning of
> their non-standard bits.
So when you go away and some other developer tries to debug a problem
in this area, then what happens? Do they just guess what those bits
mean?
Sorry, this sort of situation is unacceptable in this modern day and
age. You'll need to work this out before I'm willing to take the
patch.
next prev parent reply other threads:[~2009-09-04 22:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-31 23:08 [PATCH] forcedeth: updated phy errata Ayaz Abdulla
2009-09-03 6:22 ` David Miller
2009-09-04 13:57 ` Ayaz Abdulla
2009-09-04 22:00 ` David Miller [this message]
2009-09-04 17:22 ` Ayaz Abdulla
2009-09-04 22:54 ` David Miller
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=20090904.150015.247320928.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=aabdulla@nvidia.com \
--cc=akpm@osdl.org \
--cc=manfred@colorfullife.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).