Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Janusz Dziedzic <janusz.dziedzic@tieto.com>
Cc: linux-wireless@vger.kernel.org, mcgrof@do-not-panic.com,
	linville@tuxdriver.com
Subject: Re: [PATCH 4/4] cfg80211: DFS get CAC time from regulatory
Date: Fri, 21 Feb 2014 09:54:51 +0100	[thread overview]
Message-ID: <1392972891.4346.39.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1392231266-28479-4-git-send-email-janusz.dziedzic@tieto.com> (sfid-20140212_195441_189422_FB19079E)

On Wed, 2014-02-12 at 19:54 +0100, Janusz Dziedzic wrote:

> +	if (t2 > t1)
> +		t1 = t2;
> +
> +	return t1;

return max(t1, t2);

Is there any real reason to split patches 3/4? It seems to me they
should go together.

johannes


  reply	other threads:[~2014-02-21  8:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-12 18:54 [PATCH 1/4] cfg80211: regulatory, introduce DFS CAC time Janusz Dziedzic
2014-02-12 18:54 ` [PATCH 2/4] cfg80211: parse DFS CAC time for internal regdb option Janusz Dziedzic
2014-02-12 18:54 ` [PATCH 3/4] cfg80211/mac80211: DFS pass CAC time as a parameter Janusz Dziedzic
2014-02-21  8:53   ` Johannes Berg
2014-02-12 18:54 ` [PATCH 4/4] cfg80211: DFS get CAC time from regulatory Janusz Dziedzic
2014-02-21  8:54   ` Johannes Berg [this message]
2014-02-12 18:54 ` [PATCH] wireless-regdb: add DFS CAC time parameter Janusz Dziedzic
2014-02-12 18:54 ` [PATCH] crda: add DFS CAC time support Janusz Dziedzic
2014-02-12 18:54 ` [PATCH] iw: handle DFS CAC time param Janusz Dziedzic
2014-02-19  0:31 ` [PATCH 1/4] cfg80211: regulatory, introduce DFS CAC time Luis R. Rodriguez
2014-02-19 11:03 ` Johannes Berg
2014-02-19 11:27   ` Janusz Dziedzic
2014-02-19 11:28     ` Johannes Berg
2014-02-19 22:11       ` Luis R. Rodriguez
2014-02-20  7:12         ` Janusz Dziedzic
2014-02-22  0:31           ` Luis R. Rodriguez
2014-02-21  8:52 ` Johannes Berg
2014-02-21  9:47   ` Janusz Dziedzic
2014-02-21  9:55     ` Johannes Berg
2014-02-21 10:09       ` Janusz Dziedzic
2014-02-21 10:11         ` Johannes Berg

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=1392972891.4346.39.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=janusz.dziedzic@tieto.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mcgrof@do-not-panic.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