From: Johannes Berg <johannes@sipsolutions.net>
To: "Peer, Ilan" <ilan.peer@intel.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"mcgrof@suse.com" <mcgrof@suse.com>
Subject: Re: [PATCH v2] cfg80211: Stop calling crda if it is not responsive
Date: Wed, 01 Apr 2015 11:22:54 +0200 [thread overview]
Message-ID: <1427880174.3428.4.camel@sipsolutions.net> (raw)
In-Reply-To: <CB3B3D4774441E42AA3EA0E1BA8230A04D092DC4@HASMSX106.ger.corp.intel.com>
On Wed, 2015-04-01 at 09:19 +0000, Peer, Ilan wrote:
> > Applied, but I put the condition in a place before printing more messages, and
> > changed the messages back to the original ones.
> >
>
> But this would miss the update in case that the internal DB is also used.
Hm, true, I'll move the prints later instead.
johannes
next prev parent reply other threads:[~2015-04-01 9:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 12:15 [PATCH v2] cfg80211: Stop calling crda if it is not responsive Ilan Peer
2015-04-01 8:51 ` Johannes Berg
2015-04-01 9:19 ` Peer, Ilan
2015-04-01 9:22 ` Johannes Berg [this message]
2015-04-01 11:37 ` Peer, Ilan
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=1427880174.3428.4.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ilan.peer@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@suse.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).