[PATCH] Fixed coding style issues raised by checkpatch.

[Greg KH]

On Sat, Oct 10, 2020 at 01:32:00AM +0100, Tabot Kevin wrote:
> This patch fixes the following:
> - Made sure alignment matched open parenthesis.
> 
> Signed-off-by: Tabot Kevin <tabot.kevin at gmail.com>
> ---
>  drivers/staging/greybus/audio_module.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/staging/greybus/audio_module.c b/drivers/staging/greybus/audio_module.c
> index c52c4f3..a243d60 100644
> --- a/drivers/staging/greybus/audio_module.c
> +++ b/drivers/staging/greybus/audio_module.c
> @@ -175,8 +175,8 @@ static int gbaudio_codec_request_handler(struct gb_operation *op)
>  }
>  
>  static int gb_audio_add_mgmt_connection(struct gbaudio_module_info *gbmodule,
> -				struct greybus_descriptor_cport *cport_desc,
> -				struct gb_bundle *bundle)
> +					struct greybus_descriptor_cport *cport_desc,
> +					struct gb_bundle *bundle)
>  {
>  	struct gb_connection *connection;
>  
> @@ -199,8 +199,8 @@ static int gb_audio_add_mgmt_connection(struct gbaudio_module_info *gbmodule,
>  }
>  
>  static int gb_audio_add_data_connection(struct gbaudio_module_info *gbmodule,
> -				struct greybus_descriptor_cport *cport_desc,
> -				struct gb_bundle *bundle)
> +					struct greybus_descriptor_cport *cport_desc,
> +					struct gb_bundle *bundle)
>  {
>  	struct gb_connection *connection;
>  	struct gbaudio_data_connection *dai;
> -- 
> 2.7.4

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:

- Use the tool, scripts/get_maintainer.pl on the patch, to determine
  what mailing list and developers and maintainers to cc.

- You did not specify a description of why the patch is needed, or
  possibly, any description at all, in the email body.  Please read the
  section entitled "The canonical patch format" in the kernel file,
  Documentation/SubmittingPatches for what is needed in order to
  properly describe the change.

- You did not write a descriptive Subject: for the patch, allowing Greg,
  and everyone else, to know what this patch is all about.  Please read
  the section entitled "The canonical patch format" in the kernel file,
  Documentation/SubmittingPatches for what a proper Subject: line should
  look like.

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