From: Mukesh Ojha <mojha@codeaurora.org>
To: Hariprasad Kelam <hariprasad.kelam@gmail.com>,
abbotti@mev.co.uk, hsweeten@visionengravers.com,
gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] staging: comedi: dt2811: Fix spelling mistake
Date: Sat, 6 Apr 2019 14:01:50 +0530 [thread overview]
Message-ID: <04d71813-2226-b30d-07d2-f0296d6aa900@codeaurora.org> (raw)
In-Reply-To: <20190406082319.GA4231@hari-Inspiron-1545>
On 4/6/2019 1:53 PM, Hariprasad Kelam wrote:
> changes interupts --> interrupts to fix warning reported by checkpatch
> tool
>
> Signed-off-by: Hariprasad Kelam <hariprasad.kelam@gmail.com>
Reviewed-by: Mukesh Ojha <mojha@codeaurora.org>
Cheers,
-Mukesh
> ---
> Changes in v2:
> - Make the Subject more clear by including changed file path.
> ---
> drivers/staging/comedi/drivers/dt2811.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/comedi/drivers/dt2811.c b/drivers/staging/comedi/drivers/dt2811.c
> index 05207a5..8a1f9ef 100644
> --- a/drivers/staging/comedi/drivers/dt2811.c
> +++ b/drivers/staging/comedi/drivers/dt2811.c
> @@ -52,7 +52,7 @@
> #define DT2811_ADCSR_ADBUSY BIT(5) /* r 1=A/D busy */
> #define DT2811_ADCSR_CLRERROR BIT(4)
> #define DT2811_ADCSR_DMAENB BIT(3) /* r/w 1=dma ena */
> -#define DT2811_ADCSR_INTENB BIT(2) /* r/w 1=interupts ena */
> +#define DT2811_ADCSR_INTENB BIT(2) /* r/w 1=interrupts ena */
> #define DT2811_ADCSR_ADMODE(x) (((x) & 0x3) << 0)
>
> #define DT2811_ADGCR_REG 0x01 /* r/w A/D Gain/Channel */
next prev parent reply other threads:[~2019-04-06 8:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-06 8:23 [PATCH V2] staging: comedi: dt2811: Fix spelling mistake Hariprasad Kelam
2019-04-06 8:31 ` Mukesh Ojha [this message]
2019-04-06 9:51 ` 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=04d71813-2226-b30d-07d2-f0296d6aa900@codeaurora.org \
--to=mojha@codeaurora.org \
--cc=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hariprasad.kelam@gmail.com \
--cc=hsweeten@visionengravers.com \
--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;
as well as URLs for NNTP newsgroup(s).