linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Matthias May <matthias.may@neratec.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCHv2 1/4] cfg80211: handle minimum bandwidth for quarter and half rates
Date: Thu, 11 Jun 2015 13:33:27 +0200	[thread overview]
Message-ID: <1434022407.1915.10.camel@sipsolutions.net> (raw)
In-Reply-To: <1434020791-16291-2-git-send-email-matthias.may@neratec.com> (sfid-20150611_130650_868019_E29B6AA4)

On Thu, 2015-06-11 at 13:06 +0200, Matthias May wrote:
> This patch changes the API of freq_freq_info() to take as additional argument
> the minimum bandwidth the caller can handle.
> If multiple rules match, the match with the widest bandwidth is returned.

You can't make a patch like this that breaks the compile - all these
need to be a single patch.

That said, you could get away with not changing the public
freq_reg_info() API since the callers thereof don't need it, you could
make a __freq_reg_info() that has the bandwidth and freq_reg_info() that
doesn't.

johannes


  reply	other threads:[~2015-06-11 11:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-11 11:06 [PATCHv2 0/4] Handle minimum bandwidth for quarter and half rates Matthias May
2015-06-11 11:06 ` [PATCHv2 1/4] cfg80211: handle " Matthias May
2015-06-11 11:33   ` Johannes Berg [this message]
2015-06-11 11:44   ` Johannes Berg
2015-06-11 12:46     ` Matthias May
2015-06-11 15:22       ` Johannes Berg
2015-06-11 11:06 ` [PATCHv2 2/4] ath: send minimum bandwidth to handle Matthias May
2015-06-11 11:06 ` [PATCHv2 3/4] brcm80211: " Matthias May
2015-06-11 11:06 ` [PATCHv2 4/4] rtlwifi: " Matthias May

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=1434022407.1915.10.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=matthias.may@neratec.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).