[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CA+jnaaX+n4v=G-Zqxd41c-uDVAN9yP=yqA0HK7c+Ey8o2n6ACw@mail.gmail.com>
Date: Thu, 3 Jul 2014 21:50:56 -0500
From: Chase Southwood <chase.southwood@...il.com>
To: Ian Abbott <abbotti@....co.uk>
Cc: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
hsweeten@...ionengravers.com,
"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 0/3] staging: comedi: addi_apci_1564: miscellaneous
fixes and cleanups
On Thu, Jul 3, 2014 at 4:39 AM, Ian Abbott <abbotti@....co.uk> wrote:
> On 2014-07-03 03:15, Chase Southwood wrote:
>>
>> This patchset moves a misplaced include to the proper file, swaps out an
>> overly
>> aggressive placement of apci1564_reset(), and cleans up
>> apci1564_interrupt().
>>
>> Chase Southwood (3):
>> staging: comedi: addi_apci_1564: move addi_watchdog.h include to
>> addi_apci_1564.c
>> staging: comedi: addi_apci_1564: fix use of apci1564_reset() to
>> disable DI interrupts
>> staging: comedi: addi_apci_1564: clean up apci1564_interrupt()
>>
>> .../comedi/drivers/addi-data/hwdrv_apci1564.c | 2 -
>> drivers/staging/comedi/drivers/addi_apci_1564.c | 139
>> +++++----------------
>> 2 files changed, 32 insertions(+), 109 deletions(-)
>>
>
> Looks good! You didn't list the v2 changes though. Maybe you could
> summarize them here?
I always forget to do _something_, don't I? Here are the changes:
CHANGES FROM V1:
*Patches 1 and 2 did not change.
*In Patch 3, check for interrupts from unknown sources has been removed.
*Individual status variables for the subdevices in the interrupt
handler have been swapped out in favor of a single status variable
that is reused for all subdevices.
Thanks,
Chase
>
> Reviewed-by: Ian Abbott <abbotti@....co.uk.>
>
>
> --
> -=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@....co.uk> )=-
> -=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=-
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists