All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daisuke Iwasa <iwadjp@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Ovidiu Panait <ovidiu.panait.oss@gmail.com>,
	Dan Carpenter <dan.carpenter@linaro.org>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	Daisuke Iwasa <iwadjp@gmail.com>
Subject: [PATCH] staging: axis-fifo: fix alignment in wait_event_interruptible()
Date: Fri,  8 May 2026 03:40:37 +0900	[thread overview]
Message-ID: <20260507184037.43613-1-iwadjp@gmail.com> (raw)

Fix a checkpatch warning for alignment in the
wait_event_interruptible() call in axis_fifo_write().

Adjust the indentation of the condition argument to align with
the opening parenthesis and wrap lines to satisfy line length
constraints.

This is a whitespace-only change with no functional impact.

Signed-off-by: Daisuke Iwasa <iwadjp@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..0ec9b6c5e7d2 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.34.1


             reply	other threads:[~2026-05-07 18:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-07 18:40 Daisuke Iwasa [this message]
2026-05-11  8:00 ` [PATCH] staging: axis-fifo: fix alignment in wait_event_interruptible() Greg Kroah-Hartman
  -- strict thread matches above, loose matches on Subject: below --
2026-04-13 14:05 deep
2026-04-13 14:45 ` Dan Carpenter
2026-03-29 11:23 Tanjim Kamal
2026-03-30 15:59 ` Greg Kroah-Hartman

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=20260507184037.43613-1-iwadjp@gmail.com \
    --to=iwadjp@gmail.com \
    --cc=dan.carpenter@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --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.