From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Kingz Tuffa <ak416_kingz@yahoo.com>
Cc: "greybus-dev@lists.linaro.org" <greybus-dev@lists.linaro.org>,
"linux-staging@lists.linux.dev" <linux-staging@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: greybus uart patch.
Date: Sun, 27 Sep 2026 18:38:39 +0200 [thread overview]
Message-ID: <2026092732-aroma-murmuring-006c@gregkh> (raw)
In-Reply-To: <378088904.1527494.1790495800044@mail.yahoo.com>
On Sun, Sep 27, 2026 at 07:56:40AM +0000, Kingz Tuffa wrote:
> From: =?utf-8?q?Roberts=20Bric=C4=ABtis?= <ak416_kingz@yahoo.com> Date: Sun, 27 Sep 2026 10:48:38 +0000 Subject: [PATCH] staging: greybus: uart: fix alignment to match open parenthesis MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Clean up the coding style in uart.c by aligning the arguments of wait_for_completion_timeout() properly. Signed-off-by: Roberts Bricītis <ak416_kingz@yahoo.com> --- drivers/staging/greybus/uart.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/greybus/uart.c b/drivers/staging/greybus/uart.c index 24b4dab069c3..3d5ff4f65555 100644 --- a/drivers/staging/greybus/uart.c +++ b/drivers/staging/greybus/uart.c @@ -318,7 +318,7 @@ static int gb_uart_wait_for_all_credits(struct gb_tty *gb_tty) return 0; ret = wait_for_completion_timeout(&gb_tty->credits_complete, - msecs_to_jiffies(GB_UART_CREDIT_WAIT_TIMEOUT_MSEC)); + msecs_to_jiffies(GB_UART_CREDIT_WAIT_TIMEOUT_MSEC)); if (!ret) { dev_err(&gb_tty->gbphy_dev->dev, "time out waiting for credits\n"); -- 2.55.0
Something went really wrong :(
prev parent reply other threads:[~2026-09-27 16:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <378088904.1527494.1790495800044.ref@mail.yahoo.com>
2026-09-27 7:56 ` greybus uart patch Kingz Tuffa
2026-09-27 16:38 ` gregkh [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=2026092732-aroma-murmuring-006c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ak416_kingz@yahoo.com \
--cc=greybus-dev@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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.