From: Greg KH <gregkh@linuxfoundation.org>
To: Jeffin Philip <jeffinphilip14@gmail.com>
Cc: ovidiu.panait.oss@gmail.com, error27@gmail.com,
gustavopiazdasilva2102@gmail.com, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: axis-fifo: Fix alignment in open parentheses
Date: Tue, 28 Jul 2026 09:08:10 +0200 [thread overview]
Message-ID: <2026072848-crinkly-resolved-cc55@gregkh> (raw)
In-Reply-To: <20260723163110.126797-1-jeffinphilip14@gmail.com>
On Thu, Jul 23, 2026 at 10:01:10PM +0530, Jeffin Philip wrote:
> Fix checkpatch error:
> "Alignment should match open parenthesis" in axis-fifo.c
>
> Thanks,
> Jeffin
No need for this in the middle of a changelog text :)
>
> Signed-off-by: Jeffin Philip <jeffinphilip14@gmail.com>
> ---
> drivers/staging/axis-fifo/axis-fifo.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/staging/axis-fifo/axis-fifo.c b/drivers/staging/axis-fifo/axis-fifo.c
> index 3aa2aa870ea9..e8facc9b429b 100644
> --- a/drivers/staging/axis-fifo/axis-fifo.c
> +++ b/drivers/staging/axis-fifo/axis-fifo.c
> @@ -246,7 +246,8 @@ static ssize_t axis_fifo_write(struct file *f, const char __user *buf,
> mutex_lock(&fifo->write_lock);
>
> ret = wait_event_interruptible(fifo->write_queue,
> - ioread32(fifo->base_addr + XLLF_TDFV_OFFSET) >= words_to_write);
> + ioread32(fifo->base_addr +
> + XLLF_TDFV_OFFSET) >= words_to_write);
> if (ret)
> goto end_unlock;
> }
> --
> 2.55.0
>
This change:
https://lore.kernel.org/r/20260721030618.27784-1-amnashamraze1@gmail.com
does it a bit better, right?
thanks,
greg k-h
prev parent reply other threads:[~2026-07-28 7:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 16:31 [PATCH] staging: axis-fifo: Fix alignment in open parentheses Jeffin Philip
2026-07-28 7:08 ` Greg KH [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=2026072848-crinkly-resolved-cc55@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=error27@gmail.com \
--cc=gustavopiazdasilva2102@gmail.com \
--cc=jeffinphilip14@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=ovidiu.panait.oss@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 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.