From: Johannes Berg <johannes@sipsolutions.net>
To: Fariya Fathima <fariya.f@redpinesignals.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 3.14.0-rc5 v3 1/10] rsi: Adding RS9113 driver files
Date: Wed, 05 Mar 2014 19:08:19 +0100 [thread overview]
Message-ID: <1394042899.5275.47.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <-1822401706-40502@mail.redpinesignals.com>
On Wed, 2014-03-05 at 23:28 +0530, Fariya Fathima wrote:
> The num_debugfs entries corresponds to the number of debugfs entries
> to be created by the core layer. Our driver has support for 2
> interfaces - SDIO & USB. The SDIO driver intends to create 4 debugfs
> entries and the USB driver intends to create 3. This information is
> indicated to the core layer by initializing the num_debufs entries,
> depending on the interface.
Yeah I got confused with this. I guess it's OK, although likely to break
in the future? Maybe the SDIO layer should provide that one debugfs
handler itself, rather than having it in the core, so that this
distinction isn't needed?
> These seem odd ... maybe they should at least come with comments
> about
> how generic kernel functionality can't be used and why it needs
> another
> abstraction layer?
> We did put in various fields inside the rsi_event and rsi_thread
> structs to create a slight abstraction. I hope that is fine.
I have no issues with that really, it just seems odd, but maybe it just
means the kernel functionality isn't precisely what you need.
johannes
next parent reply other threads:[~2014-03-05 18:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <-1822401706-40502@mail.redpinesignals.com>
2014-03-05 18:08 ` Johannes Berg [this message]
2014-03-03 7:55 [PATCH 3.14.0-rc5 v3 1/10] rsi: Adding RS9113 driver files Fariya Fatima
2014-03-04 18:38 ` John W. Linville
2014-03-04 20:08 ` Jonas Gorski
2014-03-04 20:13 ` John W. Linville
2014-03-05 10:49 ` 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=1394042899.5275.47.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=fariya.f@redpinesignals.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).