linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: pushkar.iit@gmail.com (Pushkar Jambhlekar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] vc04_services: Fixing coding guideline error
Date: Thu, 16 Mar 2017 11:01:38 +0530	[thread overview]
Message-ID: <CAMvNc9BT7_5Hu2iFxd1cbEY64jzQxCEZhdgU8cm_p_SDnZFZhQ@mail.gmail.com> (raw)
In-Reply-To: <1489559468-46932-1-git-send-email-pushkar.iit@gmail.com>

Any comment?

On Wed, Mar 15, 2017 at 12:01 PM, Pushkar Jambhlekar
<pushkar.iit@gmail.com> wrote:
> Fixing 'if' block coding style. '{' should follow 'if' for multiline block
>
> Signed-off-by: Pushkar Jambhlekar <pushkar.iit@gmail.com>
> ---
>  drivers/staging/vc04_services/interface/vchiq_arm/vchiq_shim.c | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_shim.c b/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_shim.c
> index 48984ab..ca896a5 100644
> --- a/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_shim.c
> +++ b/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_shim.c
> @@ -797,8 +797,7 @@ int32_t vchi_get_peer_version(const VCHI_SERVICE_HANDLE_T handle, short *peer_ve
>  {
>         int32_t ret = -1;
>         SHIM_SERVICE_T *service = (SHIM_SERVICE_T *)handle;
> -       if (service)
> -       {
> +       if (service) {
>                 VCHIQ_STATUS_T status;
>
>                 status = vchiq_get_peer_version(service->handle, peer_version);
> --
> 2.7.4
>



-- 
Jambhlekar Pushkar Arun
M.Tech IIT Roorkee

  reply	other threads:[~2017-03-16  5:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-15  6:31 [PATCH] vc04_services: Fixing coding guideline error Pushkar Jambhlekar
2017-03-16  5:31 ` Pushkar Jambhlekar [this message]
2017-03-16  6:36   ` Greg Kroah-Hartman
2017-03-16 11:40   ` Dan Carpenter
2017-03-21  7:37 ` Greg Kroah-Hartman

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=CAMvNc9BT7_5Hu2iFxd1cbEY64jzQxCEZhdgU8cm_p_SDnZFZhQ@mail.gmail.com \
    --to=pushkar.iit@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).