From: Ian Abbott <abbotti@mev.co.uk>
To: Ranjith Thangavel <ranjithece24@gmail.com>, gregkh@linuxfoundation.org
Cc: hsweeten@visionengravers.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] comedi: ni_6527: Fix coding style - use BIT macro
Date: Wed, 18 Nov 2015 16:02:49 +0000 [thread overview]
Message-ID: <564CA129.4000603@mev.co.uk> (raw)
In-Reply-To: <1447506803-11050-1-git-send-email-ranjithece24@gmail.com>
On 14/11/15 13:13, Ranjith Thangavel wrote:
> BIT macro is used for defining BIT location instead of
> shifting operator - coding style issue
>
> Signed-off-by: Ranjith Thangavel <ranjithece24@gmail.com>
> ---
> drivers/staging/comedi/drivers/ni_6527.c | 27 ++++++++++++++-------------
> 1 file changed, 14 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/staging/comedi/drivers/ni_6527.c b/drivers/staging/comedi/drivers/ni_6527.c
> index b340b98..1903d64 100644
> --- a/drivers/staging/comedi/drivers/ni_6527.c
> +++ b/drivers/staging/comedi/drivers/ni_6527.c
> @@ -32,6 +32,8 @@
>
> #include "../comedi_pci.h"
>
> +#include "comedi_fc.h"
> +
That part seems to have been added in by mistake.
> /*
> * PCI BAR1 - Register memory map
> *
> @@ -52,13 +54,13 @@
> #define NI6527_FILT_ENA_REG(x) (0x0c + (x))
> #define NI6527_STATUS_REG 0x14
> #define NI6527_STATUS_IRQ BIT(2)
> -#define NI6527_STATUS_OVERFLOW BIT(1)
> +#define NI6527_STATUS_OVERFLOW BIT(1)
> #define NI6527_STATUS_EDGE BIT(0)
> #define NI6527_CTRL_REG 0x15
> #define NI6527_CTRL_FALLING BIT(4)
> #define NI6527_CTRL_RISING BIT(3)
> #define NI6527_CTRL_IRQ BIT(2)
> -#define NI6527_CTRL_OVERFLOW BIT(1)
> +#define NI6527_CTRL_OVERFLOW BIT(1)
> #define NI6527_CTRL_EDGE BIT(0)
> #define NI6527_CTRL_DISABLE_IRQS 0
> #define NI6527_CTRL_ENABLE_IRQS (NI6527_CTRL_FALLING | \
That part seems to be based on top of your previous patch that had
whitespace issues.
> @@ -221,11 +223,11 @@ static int ni6527_intr_cmdtest(struct comedi_device *dev,
>
> /* Step 1 : check if triggers are trivially valid */
>
> - err |= comedi_check_trigger_src(&cmd->start_src, TRIG_NOW);
> - err |= comedi_check_trigger_src(&cmd->scan_begin_src, TRIG_OTHER);
> - err |= comedi_check_trigger_src(&cmd->convert_src, TRIG_FOLLOW);
> - err |= comedi_check_trigger_src(&cmd->scan_end_src, TRIG_COUNT);
> - err |= comedi_check_trigger_src(&cmd->stop_src, TRIG_COUNT);
> + err |= cfc_check_trigger_src(&cmd->start_src, TRIG_NOW);
> + err |= cfc_check_trigger_src(&cmd->scan_begin_src, TRIG_OTHER);
> + err |= cfc_check_trigger_src(&cmd->convert_src, TRIG_FOLLOW);
> + err |= cfc_check_trigger_src(&cmd->scan_end_src, TRIG_COUNT);
> + err |= cfc_check_trigger_src(&cmd->stop_src, TRIG_COUNT);
>
> if (err)
> return 1;
> @@ -235,12 +237,11 @@ static int ni6527_intr_cmdtest(struct comedi_device *dev,
>
> /* Step 3: check if arguments are trivially valid */
>
> - err |= comedi_check_trigger_arg_is(&cmd->start_arg, 0);
> - err |= comedi_check_trigger_arg_is(&cmd->scan_begin_arg, 0);
> - err |= comedi_check_trigger_arg_is(&cmd->convert_arg, 0);
> - err |= comedi_check_trigger_arg_is(&cmd->scan_end_arg,
> - cmd->chanlist_len);
> - err |= comedi_check_trigger_arg_is(&cmd->stop_arg, 0);
> + err |= cfc_check_trigger_arg_is(&cmd->start_arg, 0);
> + err |= cfc_check_trigger_arg_is(&cmd->scan_begin_arg, 0);
> + err |= cfc_check_trigger_arg_is(&cmd->convert_arg, 0);
> + err |= cfc_check_trigger_arg_is(&cmd->scan_end_arg, cmd->chanlist_len);
> + err |= cfc_check_trigger_arg_is(&cmd->stop_arg, 0);
>
> if (err)
> return 3;
>
As Dan Carpenter pointed out, this part has been added by mistake.
The parts added by mistake seem to be a throwback to an earlier kernel
version.
--
-=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=-
-=( Web: http://www.mev.co.uk/ )=-
next prev parent reply other threads:[~2015-11-18 16:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-14 13:13 [PATCH] comedi: ni_6527: Fix coding style - use BIT macro Ranjith Thangavel
2015-11-16 14:33 ` Dan Carpenter
2015-11-18 16:02 ` Ian Abbott [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-11-16 16:56 Ranjith Thangavel
2015-11-18 16:36 ` Ian Abbott
2015-11-11 16:14 Ranjith Thangavel
2015-11-12 17:59 ` Ian Abbott
2015-11-09 17:57 Ranjith T
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=564CA129.4000603@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hsweeten@visionengravers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ranjithece24@gmail.com \
/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.