On Fri, Apr 11, 2014 at 3:29 PM, Janusz Dziedzic
<janusz.dziedzic@xxxxxxxxx> wrote:
> Track CRDA requests and handle timeout
> when no answer from CRDA.
> This could happen during startup when
> crda binary is not available.
[...]
> @@ -1864,7 +1865,8 @@ static void reg_process_pending_hints(void)
>
> /* When last_request->processed becomes true this will be rescheduled */
> if (lr && !lr->processed) {
> - REG_DBG_PRINT("Pending regulatory request, waiting for it to be processed...\n");
> + REG_DBG_PRINT("Pending %s regulatory request, waiting for it to be processed...\n",
> + reg_initiator_name(lr->initiator));
> return;
The patch is good, but what's why not also apply Luis' original
("cfg80211: fix processing world regdomain when non modular") + my
suggested fix for the issue there?
The way I see it, the sooner we retry the better. Why should I see
this print instead of trying to re-process the hint?
Arik
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
