Linux kernel staging patches
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Pramod Maurya <pramod.nexgen@gmail.com>
Cc: ovidiu.panait.oss@gmail.com, gustavopiazdasilva2102@gmail.com,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: axis-fifo: Fix alignment of wait_event_interruptible arguments
Date: Tue, 7 Jul 2026 12:01:21 +0200	[thread overview]
Message-ID: <2026070753-deprecate-storm-b4be@gregkh> (raw)
In-Reply-To: <20260523193845.195475-1-pramod.nexgen@gmail.com>

On Sat, May 23, 2026 at 03:38:45PM -0400, Pramod Maurya wrote:
> To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Ovidiu Panait <ovidiu.panait.oss@gmail.com>
> Cc: Gustavo Piaz da Silva <gustavopiazdasilva2102@gmail.com>
> Cc: linux-staging@lists.linux.dev
> Cc: linux-kernel@vger.kernel.org

Something went wrong, this shouldn't be in the body of the email :(

> 
> The second argument to wait_event_interruptible() was indented with a
> single tab instead of being aligned to the opening parenthesis. Since
> the fully-aligned form exceeds 80 columns, break the condition at the
> comparison operator and align the continuation line to the opening
> parenthesis.
> 
> Fixes the following checkpatch.pl warning:
>   CHECK: Alignment should match open parenthesis
> 
> Signed-off-by: Pramod Maurya <pramod.nexgen@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..1c34de020cf8 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);

No, the original is easier to understand, right?

thanks,

greg k-h

  reply	other threads:[~2026-07-07 10:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-23 19:38 [PATCH] staging: axis-fifo: Fix alignment of wait_event_interruptible arguments Pramod Maurya
2026-07-07 10:01 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-05-09 17:15 Pramod Maurya
2026-05-10 16:09 ` Greg KH

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=2026070753-deprecate-storm-b4be@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=gustavopiazdasilva2102@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=ovidiu.panait.oss@gmail.com \
    --cc=pramod.nexgen@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