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 00/11] staging: comedi: move comedi_fc functionality into core
Date: Tue, 16 Sep 2014 08:44:28 +0100 [thread overview]
Message-ID: <5417EA5C.3090405@mev.co.uk> (raw)
In-Reply-To: <DC148C5AA1CEBA4E87973D432B1C2D8825FA1BE3@P3PWEX4MB008.ex4.secureserver.net>
On 15/09/14 19:21, Hartley Sweeten wrote:
> On Monday, September 15, 2014 5:46 AM, Ian Abbott wrote:
>> The "comedi_fc" module contains a few functions for use by several
>> low-level comedi drivers. Since they are used by quite a few drivers,
>> it seems useful to migrate their functionality to the core "comedi"
>> module, renaming them in the process, while keeping the original
>> function names in "drivers/comedi_fc.h" available for now. This set of
>> patches accomplishes that.
>>
>> The next stages after this will be to migrate the remaining inline
>> functions from "drivers/comedi_fc.h" (possibly making them externally
>> exported functions, although they are rather short), and then to update
>> the low-level drivers to call the functions with the new names,
>> eliminating the need to include "comedi_fc.h". Then
>> "drivers/comedi_fc.h" can be removed as well.
>>
>> Note that PATCH 10 has a couple of checkpatch warnings due to
>> changing an existing block comment in non-standard block-comment style.
>>
>> PATCH 11 has a checkpatch warning to check whether MAINTAINERS needs
>> updating. It doesn't.
>>
>> PATCH 11 might conflict with some other patch series that haven't been
>> committed yet.
>>
>> 01) staging: comedi: add comedi_bytes_per_scan()
>> 02) staging: comedi: comedi_fc: use comedi_bytes_per_scan()
>> 03) staging: comedi: add comedi_inc_scan_progress()
>> 04) staging: comedi: comedi_fc: use comedi_inc_scan_progress()
>> 05) staging: comedi: add comedi_handle_events()
>> 06) staging: comedi: comedi_fc: cfc_write_array_to_buffer() data is
>> const
>> 07) staging: comedi: add comedi_write_array_to_buffer()
>> 08) staging: comedi: comedi_fc.h: use comedi_write_array_to_buffer()
>> 09) staging: comedi: add comedi_read_array_from_buffer()
>> 10) staging: comedi: migrate copyrights from "comedi_fc.c"
>> 11) staging: comedi: remove comedi_fc module
>>
>> drivers/staging/comedi/Kconfig | 31 -------
>> drivers/staging/comedi/comedi_buf.c | 66 +++++++++++++++
>> drivers/staging/comedi/comedidev.h | 11 +++
>> drivers/staging/comedi/drivers.c | 95 +++++++++++++++++++++
>> drivers/staging/comedi/drivers/Makefile | 1 -
>> drivers/staging/comedi/drivers/comedi_fc.c | 132 -----------------------------
>> drivers/staging/comedi/drivers/comedi_fc.h | 40 ++++++---
>> 7 files changed, 201 insertions(+), 175 deletions(-)
>
> Ian,
>
> Other than I think the comedi_fc.c functions should be migrated to
> comedi_buf.c instead of drivers.c I have not problems with this.
I think it's debatable. The only one of the three functions you
mentioned that touches the buffer is comedi_inc_scan_progress(), and I'd
rather keep that with comedi_bytes_per_scan().
> And, patch 11 does have a conflict with your "... use dma_alloc_coherent..."
> patches.
Yes, I'll have to fix up one or the other, depending which gets applied
first (unless git can magically sort it out with a three way merge).
> But,
>
> Reviewed-by: H Hartley Sweeten <hsweeten@visionengravers.com>
>
Thanks!
--
-=( 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:[~2014-09-16 7:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 12:45 Ian Abbott
2014-09-15 12:45 ` [PATCH 01/11] staging: comedi: add comedi_bytes_per_scan() Ian Abbott
2014-09-15 18:12 ` Hartley Sweeten
2014-09-15 12:45 ` [PATCH 02/11] staging: comedi: comedi_fc: use comedi_bytes_per_scan() Ian Abbott
2014-09-15 12:45 ` [PATCH 03/11] staging: comedi: add comedi_inc_scan_progress() Ian Abbott
2014-09-15 18:14 ` Hartley Sweeten
2014-09-15 12:46 ` [PATCH 04/11] staging: comedi: comedi_fc: use comedi_inc_scan_progress() Ian Abbott
2014-09-15 12:46 ` [PATCH 05/11] staging: comedi: add comedi_handle_events() Ian Abbott
2014-09-15 18:17 ` Hartley Sweeten
2014-09-15 12:46 ` [PATCH 06/11] staging: comedi: comedi_fc: cfc_write_array_to_buffer() data is const Ian Abbott
2014-09-15 12:46 ` [PATCH 07/11] staging: comedi: add comedi_write_array_to_buffer() Ian Abbott
2014-09-15 12:46 ` [PATCH 08/11] staging: comedi: comedi_fc.h: use comedi_write_array_to_buffer() Ian Abbott
2014-09-15 12:46 ` [PATCH 09/11] staging: comedi: add comedi_read_array_from_buffer() Ian Abbott
2014-09-15 12:46 ` [PATCH 10/11] staging: comedi: migrate copyrights from "comedi_fc.c" Ian Abbott
2014-09-15 12:46 ` [PATCH 11/11] staging: comedi: remove comedi_fc module Ian Abbott
2014-09-15 18:07 ` Hartley Sweeten
2014-09-15 18:21 ` [PATCH 00/11] staging: comedi: move comedi_fc functionality into core Hartley Sweeten
2014-09-16 7:44 ` Ian Abbott [this message]
2014-09-16 16: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=5417EA5C.3090405@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®