linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Hridesh MG <hridesh699@gmail.com>
Cc: linux-rpi-kernel@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	Florian Fainelli <florian.fainelli@broadcom.com>,
	Broadcom internal kernel review list
	<bcm-kernel-feedback-list@broadcom.com>,
	Umang Jain <umang.jain@ideasonboard.com>,
	Stefan Wahren <wahrenst@gmx.net>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Kieran Bingham <kieran.bingham@ideasonboard.com>
Subject: Re: [PATCH] staging: vchiq_core: Fix code indent errors
Date: Wed, 9 Oct 2024 12:00:26 +0200	[thread overview]
Message-ID: <2024100911-casket-shading-a22f@gregkh> (raw)
In-Reply-To: <20241007152214.23240-1-hridesh699@gmail.com>

On Mon, Oct 07, 2024 at 08:52:12PM +0530, Hridesh MG wrote:
> Replace spaces with tabs to adhere to kernel coding style.
> 
> Reported by checkpatch:
> 
> ERROR: code indent should use tabs where possible
> 
> Signed-off-by: Hridesh MG <hridesh699@gmail.com>
> ---
>  .../vc04_services/interface/vchiq_arm/vchiq_core.c | 14 +++++++-------
>  1 file changed, 7 insertions(+), 7 deletions(-)
> 
> diff --git a/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_core.c b/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_core.c
> index 1f94db6e0cd9..3f3ef1ca7154 100644
> --- a/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_core.c
> +++ b/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_core.c
> @@ -2761,13 +2761,13 @@ vchiq_bulk_xfer_queue_msg_interruptible(struct vchiq_service *service,
>  		state->id, service->localport, dir_char, queue->local_insert,
>  		queue->remote_insert, queue->process);
>  
> -        if (bulk_waiter) {
> -                bulk_waiter->bulk = bulk;
> -                if (wait_for_completion_interruptible(&bulk_waiter->event))
> -                        status = -EAGAIN;
> -                else if (bulk_waiter->actual == VCHIQ_BULK_ACTUAL_ABORTED)
> -                        status = -EINVAL;
> -        }
> +	if (bulk_waiter) {
> +		bulk_waiter->bulk = bulk;
> +		if (wait_for_completion_interruptible(&bulk_waiter->event))
> +			status = -EAGAIN;
> +		else if (bulk_waiter->actual == VCHIQ_BULK_ACTUAL_ABORTED)
> +			status = -EINVAL;
> +	}
>  
>  	return status;
>  
> -- 
> 2.46.1
> 
> 

No longer applies to the tree due to other changes that were submitted
before you, sorry.

greg k-h


      parent reply	other threads:[~2024-10-09 10:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-07 15:22 [PATCH] staging: vchiq_core: Fix code indent errors Hridesh MG
2024-10-07 15:43 ` Dan Carpenter
2024-10-09 10:00 ` Greg Kroah-Hartman [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=2024100911-casket-shading-a22f@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=florian.fainelli@broadcom.com \
    --cc=hridesh699@gmail.com \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=umang.jain@ideasonboard.com \
    --cc=wahrenst@gmx.net \
    /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;
as well as URLs for NNTP newsgroup(s).