Linux wireless drivers development
 help / color / mirror / Atom feed
From: Luciano Coelho <coelho@ti.com>
To: Guy Eilam <guy@wizery.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v3] wl12xx: use 2 spare TX blocks for GEM cipher
Date: Thu, 25 Aug 2011 10:18:44 +0300	[thread overview]
Message-ID: <1314256724.2296.246.camel@cumari> (raw)
In-Reply-To: <1313513352-32316-1-git-send-email-guy@wizery.com>

On Tue, 2011-08-16 at 19:49 +0300, Guy Eilam wrote: 
> Add tx_spare_blocks member to the wl1271 struct
> for more generic configuration of the amount
> of spare TX blocks that should be used.
> The default value is 1.
> In case GEM cipher is used by the STA, we need
> 2 spare TX blocks instead of just 1.
> 
> Signed-off-by: Guy Eilam <guy@wizery.com>
> ---

Applied, thanks!

-- 
Cheers,
Luca.


      parent reply	other threads:[~2011-08-25  7:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-16 16:49 [PATCH v3] wl12xx: use 2 spare TX blocks for GEM cipher Guy Eilam
2011-08-16 19:06 ` Arik Nemtsov
2011-08-22  7:41 ` Luciano Coelho
2011-08-25  7:18 ` Luciano Coelho [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=1314256724.2296.246.camel@cumari \
    --to=coelho@ti.com \
    --cc=guy@wizery.com \
    --cc=linux-wireless@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