From: Ian Abbott <abbotti@mev.co.uk>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Ian Abbott <ian.abbott@mev.co.uk>,
H Hartley Sweeten <hartleys@visionengravers.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"fmhess@users.sourceforge.net" <fmhess@users.sourceforge.net>
Subject: Re: [PATCH] staging: comedi: Convert struct addi_board initialization to C99 format
Date: Thu, 17 May 2012 16:57:46 +0100 [thread overview]
Message-ID: <4FB51FFA.3090800@mev.co.uk> (raw)
In-Reply-To: <20120517133221.GB5090@kroah.com>
On 2012/05/17 02:32 PM, Greg KH wrote:
> On Thu, May 17, 2012 at 07:45:08AM +0100, Ian Abbott wrote:
>> On 17/05/12 07:15, H Hartley Sweeten wrote:
>>> Wednesday, May 16, 2012 7:18 PM, Greg KH wrote:
>>>> On Wed, May 16, 2012 at 05:51:56PM -0700, H Hartley Sweeten wrote:
>>>>> Convert the struct addi_board initialization to C99 format and remove
>>>>> all the NULL or 0 initializers. This makes maintaining and editing the
>>>>> code simpler and less error prone.
>>>> Nice job, this driver is a pain to read...
>>>
>>> Thanks. I agree... I've been avoiding the addi drivers until now.
>>> Anytime a C file has an #include "something.c" it makes me
>>> shudder...
>>>
>>> I've been thinking that the addi stuff should really be broken up
>>> into some library modules with exported symbols for the individual
>>> addi drivers to use. I need to look a bit closer at them to see if
>>> this would work. Right now the whole thing is a bit of a mess.
>>
>> TBH, I don't know how they got accepted into Comedi in the first
>> place. They tend to do their own thing as far as comedi instruction
>> handling goes. I've no idea who's using them. It makes me shudder,
>> too! Did I mention the use of floating point in some of their
>> drivers that we had to disable?
>
> I thought a few years ago, either you, or someone else, said it would be
> good to just delete them entirely. Or am I making that up and just wish
> it would be so? :)
I can't remember at my age!
There was a guy who works for Addi-Data (Krauth Julien) who had trouble
submitting patches to you directly (I was CC'd) back in
September/October 2011, so I guess they'd be unhappy if the drivers were
removed altogether!
--
-=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=-
-=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=-
next prev parent reply other threads:[~2012-05-17 15:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 0:51 [PATCH] staging: comedi: Convert struct addi_board initialization to C99 format H Hartley Sweeten
2012-05-17 2:18 ` Greg KH
2012-05-17 6:15 ` H Hartley Sweeten
2012-05-17 6:45 ` Ian Abbott
2012-05-17 13:32 ` Greg KH
2012-05-17 15:57 ` Ian Abbott [this message]
2012-05-17 16:38 ` H Hartley Sweeten
2012-05-17 18:28 ` Ian Abbott
2012-05-17 21:12 ` H Hartley Sweeten
2012-05-18 10:05 ` Ian Abbott
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=4FB51FFA.3090800@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=fmhess@users.sourceforge.net \
--cc=gregkh@linuxfoundation.org \
--cc=hartleys@visionengravers.com \
--cc=ian.abbott@mev.co.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.