From: Alex Elder <elder@linaro.org>
To: Till Varoquaux <till.varoquaux@gmail.com>,
kernel-janitors@vger.kernel.org, pure.logic@nexus-software.ie
Cc: devel@driverdev.osuosl.org, Alex Elder <elder@kernel.org>,
trivial@kernel.org, Johan Hovold <johan@kernel.org>,
linux-kernel@vger.kernel.org, greybus-dev@lists.linaro.org
Subject: Re: [greybus-dev] [PATCH] staging: greybus: loopback: fix a spelling error.
Date: Tue, 26 May 2020 06:47:41 -0500 [thread overview]
Message-ID: <3f610a0c-fb15-e929-0f94-447f732659a0@linaro.org> (raw)
In-Reply-To: <20200518051314.1785567-1-till.varoquaux@gmail.com>
On 5/25/20 1:10 AM, Till Varoquaux wrote:
> Successed -> succeeded.
>
> Signed-off-by: Till Varoquaux <till.varoquaux@gmail.com>
Looks good.
Reviewed-by: Alex Elder <elder@linaro.org>
> ---
> drivers/staging/greybus/loopback.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/greybus/loopback.c b/drivers/staging/greybus/loopback.c
> index 583d9708a191..2471448ba42a 100644
> --- a/drivers/staging/greybus/loopback.c
> +++ b/drivers/staging/greybus/loopback.c
> @@ -135,7 +135,7 @@ static ssize_t name##_##field##_show(struct device *dev, \
> char *buf) \
> { \
> struct gb_loopback *gb = dev_get_drvdata(dev); \
> - /* Report 0 for min and max if no transfer successed */ \
> + /* Report 0 for min and max if no transfer succeeded */ \
> if (!gb->requests_completed) \
> return sprintf(buf, "0\n"); \
> return sprintf(buf, "%" #type "\n", gb->name.field); \
>
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
prev parent reply other threads:[~2020-05-26 11:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 6:10 [PATCH] staging: greybus: loopback: fix a spelling error Till Varoquaux
2020-05-26 11:47 ` Alex Elder [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=3f610a0c-fb15-e929-0f94-447f732659a0@linaro.org \
--to=elder@linaro.org \
--cc=devel@driverdev.osuosl.org \
--cc=elder@kernel.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pure.logic@nexus-software.ie \
--cc=till.varoquaux@gmail.com \
--cc=trivial@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).