From: Adam Jaremko <adam.jaremko@gmail.com>
To: "Ratbert Po-Yu Chuang(莊博宇)" <ratbert@faraday-tech.com>
Cc: ratbert.chuang@gmail.com, netdev@vger.kernel.org
Subject: Re: linux-next ftmac100 driver
Date: Tue, 26 Apr 2011 12:08:11 -0400 [thread overview]
Message-ID: <BANLkTi=Eud9toM5HtHCSxNkPPrVEVgOCfg@mail.gmail.com> (raw)
In-Reply-To: <D557AF68929979498EDCFCBB34FFD4E82C62BC@ftcpcs78.faraday.com.tw>
> You can try to use udelay() to replace usleep_range(). I will also check this problem when I am free later.
> If you solved this problem before me, please send a message (and keep the CC list).
> It will be even better if you could submit a patch. :-)
That is what I ended up doing and am able to continue with my testing.
prev parent reply other threads:[~2011-04-26 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BANLkTin24N2D_b_RpPCQdjYn2f=C7NY2JA@mail.gmail.com>
2011-04-25 3:26 ` linux-next ftmac100 driver Ratbert Po-Yu Chuang(莊博宇)
2011-04-26 16:08 ` Adam Jaremko [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='BANLkTi=Eud9toM5HtHCSxNkPPrVEVgOCfg@mail.gmail.com' \
--to=adam.jaremko@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=ratbert.chuang@gmail.com \
--cc=ratbert@faraday-tech.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 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).