mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Matthias Oefelein <ma.oefelein@arcor.de>
Cc: devel@driverdev.osuosl.org, lisa@xenapiadmin.com,
	linux-kernel@i4.cs.fau.de, linux-kernel@vger.kernel.org,
	linux-kernel@rmueck.de
Subject: Re: [PATCH 5/6] beeceem: Fix newline issues at opening braces of conditional statements in InterfaceRx.c
Date: Wed, 8 Jan 2014 15:58:33 -0800	[thread overview]
Message-ID: <20140108235833.GA21409@kroah.com> (raw)
In-Reply-To: <1389219310-8015-6-git-send-email-ma.oefelein@arcor.de>

On Wed, Jan 08, 2014 at 11:15:09PM +0100, Matthias Oefelein wrote:
> In InterfaceRx.c, opening braces of (if-)conditionals are mostly dislocated, meaning they are found behind an extra line break after the conditional statement.
> This patch moves the opening braces accordingly as specified by the official conding style guidelines.

Please properly line-wrap your changelog comments at 72 columns like git
asks you to when you type them in...

thanks,

greg k-h

  reply	other threads:[~2014-01-08 23:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-08 22:15 [PATCH 0/6] beeceem: Checkpatch cleanups " Matthias Oefelein
2014-01-08 22:15 ` [PATCH 1/6] beeceem: Fix missing spaces around operators and unwanted spaces around semicolons " Matthias Oefelein
2014-01-08 22:15 ` [PATCH 2/6] beeceem: Fix missing spaces between function arguments " Matthias Oefelein
2014-01-08 22:15 ` [PATCH 3/6] beeceem: Fix broken indentations " Matthias Oefelein
2014-01-08 22:15 ` [PATCH 4/6] beeceem: Fix whitespace issues at opening parentheses " Matthias Oefelein
2014-01-08 22:15 ` [PATCH 5/6] beeceem: Fix newline issues at opening braces of conditional statements " Matthias Oefelein
2014-01-08 23:58   ` Greg KH [this message]
2014-01-08 22:15 ` [PATCH 6/6] beeceem: Replace C99 comments with C89 ones and remove unneeded comments " Matthias Oefelein

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=20140108235833.GA21409@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@i4.cs.fau.de \
    --cc=linux-kernel@rmueck.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lisa@xenapiadmin.com \
    --cc=ma.oefelein@arcor.de \
    /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
Powered by JetHome