linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: linville@tuxdriver.com,
	"Thomas Hühn" <thomas@net.t-labs.tu-berlin.de>,
	linux-wireless@vger.kernel.org, nbd@nbd.name
Subject: Re: [PATCH] carl9170: make use of the new rate control API
Date: Tue, 11 Jun 2013 21:53:39 +0200	[thread overview]
Message-ID: <1370980419.8356.68.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <201306112149.09768.chunkeey@googlemail.com> (sfid-20130611_214914_098355_4B143C81)

On Tue, 2013-06-11 at 21:49 +0200, Christian Lamparter wrote:

> > > As I just saw an ath9k patch for rcu protection when ieee80211_get_tx_rates() is called.
> > > Should this be done in carl9170 as well ?
> > 
> > I think that patch is wrong actually, probably should just do the rcu
> > protection inside the function. However the patch is completely wrong
> > anyway (C isn't python) so ...
> Uh, that's confusing. We are now talking about the patch from Thomas, right?
> If so: the previous "new rate control api" feature patch for carl9170 should
> be fine in this regard.

No, Calvin Owens's patch.

johannes



  reply	other threads:[~2013-06-11 19:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-11 15:57 [PATCH] carl9170: make use of the new rate control API Thomas Huehn
2013-06-11 17:46 ` Christian Lamparter
2013-06-11 19:17   ` Thomas Hühn
2013-06-11 19:24     ` Johannes Berg
2013-06-11 19:49       ` Christian Lamparter
2013-06-11 19:53         ` Johannes Berg [this message]
2013-06-12 18:53         ` John W. Linville

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=1370980419.8356.68.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=chunkeey@googlemail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=nbd@nbd.name \
    --cc=thomas@net.t-labs.tu-berlin.de \
    /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).