staging: axis-fifo: fix alignment in wait_event_interruptible()
PATCH 1/1 staging: axis-fifo: fix alignment in wait_event_interruptible()
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.
--- drivers/staging/axis-fifo/axis-fifo.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/staging/axis-fifo/axis-fifo.c +2 -1
@@ -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; }
Signature · 1 line
2.34.1
Greg Kroah-Hartman
maintainerQuoted 32 lines · Daisuke Iwasa
Fix a checkpatch warning for alignment in the
wait_event_interruptible()call inaxis_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 <[email protected]>--- drivers/staging/axis-fifo/axis-fifo.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)drivers/staging/axis-fifo/axis-fifo.c +2
-1@@ -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; }Signature · 1 line
2.34.1
Hi,
This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him a patch that has triggered this response. He used to manually respond to these common problems, but in order to save his sanity (he kept writing the same thing over and over, yet to different people), I was created. Hopefully you will not take offence and will fix the problem in your patch and resubmit it so that it can be accepted into the Linux kernel tree.
You are receiving this message because of the following common error(s) as indicated below:
- You sent a patch that has been sent multiple times in the past few days, and is identical to ones that has been recently rejected. Please always look at the mailing list traffic to determine if you are duplicating other people's work.
If you wish to discuss this problem further, or you have questions about how to resolve this issue, please feel free to respond to this email and Greg will reply once he has dug out from the pending patches received from other developers.
thanks,
greg k-h's patch email bot