Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Tomas Winkler" <tomasw@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org, "Chatre,
	Reinette" <reinette.chatre@intel.com>
Subject: Re: TKIP patches
Date: Fri, 28 Mar 2008 10:43:27 +0300	[thread overview]
Message-ID: <1ba2fa240803280043g7d0fea74vd76691d836900c15@mail.gmail.com> (raw)
In-Reply-To: <20080328023336.GA10006@tuxdriver.com>

On Fri, Mar 28, 2008 at 5:33 AM, John W. Linville
<linville@tuxdriver.com> wrote:
>
> On Fri, Mar 28, 2008 at 03:23:28AM +0200, Tomas Winkler wrote:
>  > John, what restraining you from applying TKIP patches to wireless-testing
>  > First of all they were acked by Johannes second they need to got into
>  > wider use, most of  the people don't pick up code from the mailing
>  > list but from git directory.
>  > Even TKIP is stupid encryption schema and everybody wants see it dead
>  > it's still used. From our testing our patches reduces significantly
>  > cpu utilization and throughput.
>  > If there are any other issues please let us know
>
>  The only TKIP-related patches I have in my queue that haven't been
>  applied are some cleanups from Harvey Harrison.  What other patches
>  do you mean?  The ones from a week or so ago have already been applied.

Hmm, have to missed it somehow, my mistake.  I've seen only the revert
patches before.
Thanks
Tomas

      reply	other threads:[~2008-03-28  7:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28  1:23 TKIP patches Tomas Winkler
2008-03-28  2:33 ` John W. Linville
2008-03-28  7:43   ` Tomas Winkler [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=1ba2fa240803280043g7d0fea74vd76691d836900c15@mail.gmail.com \
    --to=tomasw@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=reinette.chatre@intel.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