From: Pramod Maurya <pramod.nexgen@gmail.com>
To: gregkh@linuxfoundation.org
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
singhigeet1729@gmail.com, jacobsfeder@gmail.com,
pramod.nexgen@gmail.com,
Ovidiu Panait <ovidiu.panait.oss@gmail.com>,
Dan Carpenter <dan.carpenter@linaro.org>,
Gustavo Piaz da Silva <gustavopiazdasilva2102@gmail.com>
Subject: [PATCH v2] staging: axis-fifo: Fix alignment of wait_event_interruptible in write path
Date: Sun, 10 May 2026 13:06:59 -0400 [thread overview]
Message-ID: <20260510170703.532005-1-pramod.nexgen@gmail.com> (raw)
Commit 87d653a894a4 ("staging: axis-fifo: Remove read/write timeout
module parameters") converted wait_event_interruptible_timeout() to
wait_event_interruptible() in both the read and write paths, but used
a single tab to indent the condition argument instead of aligning it
to the opening parenthesis.
Commit 72000df579c7 ("staging: axis-fifo: Fix indentation") corrected
the read path in axis_fifo_read(), but the write path in
axis_fifo_write() was left with the same misalignment:
ret = wait_event_interruptible(fifo->write_queue,
ioread32(fifo->base_addr + XLLF_TDFV_OFFSET) >= words_to_write);
Fix this remaining instance by aligning the condition argument and its
continuation to the opening parenthesis.
Fixes: 87d653a894a4 ("staging: axis-fifo: Remove read/write timeout module parameters")
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);
if (ret)
goto end_unlock;
}
--
2.52.0
reply other threads:[~2026-05-10 17:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260510170703.532005-1-pramod.nexgen@gmail.com \
--to=pramod.nexgen@gmail.com \
--cc=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=gustavopiazdasilva2102@gmail.com \
--cc=jacobsfeder@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=ovidiu.panait.oss@gmail.com \
--cc=singhigeet1729@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