From: Jonathan Cameron <jic23@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
lars@metafoo.de, Michael.Hennerich@analog.com, pmeerw@pmeerw.net,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: dac: Rudimentary typo fix
Date: Mon, 29 Mar 2021 11:29:19 +0100 [thread overview]
Message-ID: <20210329112919.4e690e40@jic23-huawei> (raw)
In-Reply-To: <cec8e5bf-b7be-041e-e0ea-50a41f55d79f@infradead.org>
On Mon, 22 Mar 2021 20:02:22 -0700
Randy Dunlap <rdunlap@infradead.org> wrote:
> On 3/22/21 6:22 PM, Bhaskar Chowdhury wrote:
> >
> > s/concurent/concurrent/
> >
> > Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
>
> Acked-by: Randy Dunlap <rdunlap@infradead.org>
Applied to the togreg branch of iio.git.
That will first be pushed out as testing for the autobuilders
such as 0-day to work their magic, and only later get pushed
out as a tree that I try to avoid rebasing once public.
Thanks,
Jonathan
>
> > ---
> > drivers/iio/dac/ad5766.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/iio/dac/ad5766.c b/drivers/iio/dac/ad5766.c
> > index ef1618ea6a20..79837a4b3a41 100644
> > --- a/drivers/iio/dac/ad5766.c
> > +++ b/drivers/iio/dac/ad5766.c
> > @@ -89,7 +89,7 @@ static const char * const ad5766_dither_scales[] = {
> > /**
> > * struct ad5766_state - driver instance specific data
> > * @spi: SPI device
> > - * @lock: Lock used to restrict concurent access to SPI device
> > + * @lock: Lock used to restrict concurrent access to SPI device
> > * @chip_info: Chip model specific constants
> > * @gpio_reset: Reset GPIO, used to reset the device
> > * @crt_range: Current selected output range
> > --
>
>
prev parent reply other threads:[~2021-03-29 10:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 1:22 [PATCH] iio: dac: Rudimentary typo fix Bhaskar Chowdhury
2021-03-23 3:02 ` Randy Dunlap
2021-03-29 10:29 ` Jonathan Cameron [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=20210329112919.4e690e40@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=rdunlap@infradead.org \
--cc=unixbhaskar@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 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).