From: Nick Kossifidis <mickflemm@gmail.com>
To: Bob Copeland <me@bobcopeland.com>
Cc: linville@tuxdriver.com, jirislaby@gmail.com,
lrodriguez@atheros.com, linux-wireless@vger.kernel.org,
ath5k-devel@lists.ath5k.org
Subject: Re: [PATCH 4/5] ath5k: use rx hw descriptor pointer for self-linked check
Date: Wed, 15 Apr 2009 15:12:49 +0300 [thread overview]
Message-ID: <40f31dec0904150512q206c6811j153d7ea2c73fb0e4@mail.gmail.com> (raw)
In-Reply-To: <1239796656-20646-5-git-send-email-me@bobcopeland.com>
2009/4/15 Bob Copeland <me@bobcopeland.com>:
> This patch simplifies the code used to detect when the
> self-linked DMA buffer is still in use by hardware, by
> checking the hardware's rxdp register instead of looking
> at the software buffer list.
>
> Signed-off-by: Bob Copeland <me@bobcopeland.com>
> ---
Acked-by: Nick Kossifidis <mickflemm@gmail.com>
--
GPG ID: 0xD21DB2DB
As you read this post global entropy rises. Have Fun ;-)
Nick
next prev parent reply other threads:[~2009-04-15 12:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 11:57 [PATCH 0/5] misc ath5k fixes Bob Copeland
2009-04-15 11:57 ` [PATCH 1/5] ath5k: fix initvals errors Bob Copeland
2009-04-15 12:09 ` Nick Kossifidis
2009-04-15 11:57 ` [PATCH 2/5] ath5k: use tasklet_hi_schedule for beacon queue Bob Copeland
2009-04-15 12:11 ` Nick Kossifidis
2009-04-15 11:57 ` [PATCH 3/5] ath5k: use bool for modparams Bob Copeland
2009-04-15 12:11 ` Nick Kossifidis
2009-04-15 11:57 ` [PATCH 4/5] ath5k: use rx hw descriptor pointer for self-linked check Bob Copeland
2009-04-15 12:12 ` Nick Kossifidis [this message]
2009-04-15 12:20 ` [ath5k-devel] " Daniel J Blueman
2009-04-15 12:35 ` Bob Copeland
2009-04-15 11:57 ` [PATCH 5/5] ath5k: manipulate rxlink and descriptor address under rxbuf lock Bob Copeland
2009-04-15 12:13 ` Nick Kossifidis
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=40f31dec0904150512q206c6811j153d7ea2c73fb0e4@mail.gmail.com \
--to=mickflemm@gmail.com \
--cc=ath5k-devel@lists.ath5k.org \
--cc=jirislaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.com \
--cc=me@bobcopeland.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