From: Ian Abbott <abbotti@mev.co.uk>
To: Hartley Sweeten <HartleyS@visionengravers.com>,
"driverdev-devel@linuxdriverproject.org"
<driverdev-devel@linuxdriverproject.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/5] staging: comedi: split bus support into separate modules
Date: Fri, 31 Oct 2014 23:00:54 +0000 [thread overview]
Message-ID: <545414A6.9090101@mev.co.uk> (raw)
In-Reply-To: <545412F3.60502@mev.co.uk>
On 31/10/14 22:53, Ian Abbott wrote:
> I like the idea of the core comedi module being separated from all the
> various buses. And other buses can be added easily without pulling extra
> dependencies into the core (e.g. for platform or spi devices).
And if this get's accepted, I'd like to complete the separation by
moving the PCI, USB and PCMCIA stuf out of the "comedidev.h" header into
their own headers, which obviously means small edits to most of the
low-level drivers to #include different headers. (But then,
"comedi_pci.h" could #include <linux/pci.h> for example.)
--
-=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=-
-=( Web: http://www.mev.co.uk/ )=-
next prev parent reply other threads:[~2014-10-31 23:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 17:47 Ian Abbott
2014-10-31 17:47 ` [PATCH 1/5] staging: comedi: comedidev.h: remove dummy PCI support functions Ian Abbott
2014-10-31 17:47 ` [PATCH 2/5] staging: comedi: comedidev.h: remove some #ifdefs Ian Abbott
2014-10-31 17:47 ` [PATCH 3/5] staging: comedi: split out PCMCIA support into new module Ian Abbott
2014-10-31 17:47 ` [PATCH 4/5] staging: comedi: split out USB " Ian Abbott
2014-10-31 17:47 ` [PATCH 5/5] staging: comedi: split out PCI " Ian Abbott
2014-10-31 18:19 ` [PATCH 0/5] staging: comedi: split bus support into separate modules Hartley Sweeten
2014-10-31 22:08 ` Ian Abbott
2014-10-31 22:18 ` Hartley Sweeten
2014-10-31 22:53 ` Ian Abbott
2014-10-31 23:00 ` Ian Abbott [this message]
2014-11-05 22:50 ` Greg Kroah-Hartman
2014-11-05 23:13 ` Hartley Sweeten
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=545414A6.9090101@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=HartleyS@visionengravers.com \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®