From: Ian Abbott <abbotti@mev.co.uk>
To: Colin King <colin.king@canonical.com>,
H Hartley Sweeten <hsweeten@visionengravers.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: comedi: adv_pci1710: fix spelling mistake: "droput" -> "dropout"
Date: Tue, 16 Apr 2019 11:22:49 +0100 [thread overview]
Message-ID: <dbe5e3b9-0653-53ec-1371-88c29aed7b8d@mev.co.uk> (raw)
In-Reply-To: <20190415174945.32712-1-colin.king@canonical.com>
On 15/04/2019 18:49, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> There is a spelling mistake in a dev_error message. Fix it.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
Looks good, thanks!
Reviewed-by: Ian Abbott <abbotti@mev.co.uk>
> ---
> drivers/staging/comedi/drivers/adv_pci1710.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/comedi/drivers/adv_pci1710.c b/drivers/staging/comedi/drivers/adv_pci1710.c
> index 6a93b04f1fdf..dbff0f7e7cf5 100644
> --- a/drivers/staging/comedi/drivers/adv_pci1710.c
> +++ b/drivers/staging/comedi/drivers/adv_pci1710.c
> @@ -317,7 +317,7 @@ static int pci1710_ai_read_sample(struct comedi_device *dev,
> chan = sample >> 12;
> if (chan != devpriv->act_chanlist[cur_chan]) {
> dev_err(dev->class_dev,
> - "A/D data droput: received from channel %d, expected %d\n",
> + "A/D data dropout: received from channel %d, expected %d\n",
> chan, devpriv->act_chanlist[cur_chan]);
> return -ENODATA;
> }
>
--
-=( Ian Abbott <abbotti@mev.co.uk> || Web: www.mev.co.uk )=-
-=( MEV Ltd. is a company registered in England & Wales. )=-
-=( Registered number: 02862268. Registered address: )=-
-=( 15 West Park Road, Bramhall, STOCKPORT, SK7 3JZ, UK. )=-
prev parent reply other threads:[~2019-04-16 10:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 17:49 [PATCH] staging: comedi: adv_pci1710: fix spelling mistake: "droput" -> "dropout" Colin King
2019-04-16 7:36 ` Mukesh Ojha
2019-04-16 10:22 ` Ian Abbott [this message]
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=dbe5e3b9-0653-53ec-1371-88c29aed7b8d@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=colin.king@canonical.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hsweeten@visionengravers.com \
--cc=kernel-janitors@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).