public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nandha Kumar Singaram <nandhakumar.singaram@gmail.com>
Cc: Johan Hovold <johan@kernel.org>, Alex Elder <elder@kernel.org>,
	greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org, kumaran.4353@gmail.com
Subject: Re: [PATCH 2/3] staging: greybus: Alignment should match open parenthesis
Date: Sun, 22 Oct 2023 13:19:06 +0200	[thread overview]
Message-ID: <2023102241-unloader-finalize-c3c5@gregkh> (raw)
In-Reply-To: <57d7aa177d58384bcc178f6722a8f7f6af78a536.1697969950.git.nandhakumar.singaram@gmail.com>

On Sun, Oct 22, 2023 at 03:40:57AM -0700, Nandha Kumar Singaram wrote:
> Adhere to linux coding style. Reported by checkpatch.pl:
> CHECK: Alignment should match open parenthesis
> 
> Signed-off-by: Nandha Kumar Singaram <nandhakumar.singaram@gmail.com>
> ---
>  drivers/staging/greybus/camera.c | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)

Same subject line problem :(


  reply	other threads:[~2023-10-22 11:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-22 10:38 [PATCH 0/3] staging: greybus: Coding style cleanup patches Nandha Kumar Singaram
2023-10-22 10:39 ` [PATCH 1/3] staging: greybus: Modify lines end with a '(' Nandha Kumar Singaram
2023-10-22 11:18   ` Greg Kroah-Hartman
2023-10-22 10:40 ` [PATCH 2/3] staging: greybus: Alignment should match open parenthesis Nandha Kumar Singaram
2023-10-22 11:19   ` Greg Kroah-Hartman [this message]
2023-10-22 10:42 ` [PATCH 3/3] staging: greybus: fixed prefer using ftrace warning Nandha Kumar Singaram
2023-10-22 11:19   ` Greg Kroah-Hartman
2023-10-22 12:03     ` Nandha Kumar Singaram

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=2023102241-unloader-finalize-c3c5@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=elder@kernel.org \
    --cc=greybus-dev@lists.linaro.org \
    --cc=johan@kernel.org \
    --cc=kumaran.4353@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=nandhakumar.singaram@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