From: Francois Romieu <romieu@fr.zoreil.com>
To: hayeswang <hayeswang@realtek.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
"'Ben Hutchings'" <benh@debian.org>
Subject: Re: [net-next-2.6 08/08] r8169: more 8168dp support.
Date: Wed, 5 Jan 2011 00:53:35 +0100 [thread overview]
Message-ID: <20110104235335.GA6161@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <FFFEF1293F9B4E3B81D3777F91F21B01@realtek.com.tw>
hayeswang <hayeswang@realtek.com> :
[...]
> When doing reset, the nic has to notify the embedded system and wait a response.
> However, maybe the system accesses the same register at the same time, so the
> embedded system and the driver implement the same method of software mutex to
> prevent this situation.
Thanks for the information.
I have found no 8168dp in my collection. A volunteer to test this patch with
the relevant hardware would be welcome.
--
Ueimor
prev parent reply other threads:[~2011-01-04 23:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-02 23:37 [net-next-2.6 08/08] r8169: more 8168dp support Francois Romieu
2011-01-03 12:50 ` hayeswang
2011-01-04 0:26 ` Francois Romieu
2011-01-04 2:43 ` hayeswang
2011-01-04 23:53 ` Francois Romieu [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=20110104235335.GA6161@electric-eye.fr.zoreil.com \
--to=romieu@fr.zoreil.com \
--cc=benh@debian.org \
--cc=davem@davemloft.net \
--cc=hayeswang@realtek.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