From: Johannes Berg <johannes@sipsolutions.net>
To: greearb@candelatech.com
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/2] wireless: Support wiphy_renamed hook for drivers.
Date: Mon, 11 Oct 2010 20:43:59 +0200 [thread overview]
Message-ID: <1286822639.3634.84.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1286822537-28756-1-git-send-email-greearb@candelatech.com>
On Mon, 2010-10-11 at 11:42 -0700, greearb@candelatech.com wrote:
> Some drivers may want to know when their wiphy is updated
> so that they can reuname debugfs links, etc.
I really don't like this -- we provide a debugfs directory that follows
the correct name that drivers can use, so for that particular purpose
this isn't worthwhile. And there seems no other purpose really.
johannes
next prev parent reply other threads:[~2010-10-11 18:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 18:42 [PATCH 1/2] wireless: Support wiphy_renamed hook for drivers greearb
2010-10-11 18:42 ` [PATCH 2/2] ath5k: Support wiphy_renamed operation greearb
2010-10-11 18:43 ` Johannes Berg [this message]
2010-10-11 18:46 ` [PATCH 1/2] wireless: Support wiphy_renamed hook for drivers Johannes Berg
2010-10-11 18:48 ` Ben Greear
2010-10-11 19:07 ` Ben Greear
2010-10-11 19:28 ` 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=1286822639.3634.84.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
/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).