From: Greg KH <gregkh@suse.de>
To: Timo von Holtz <tvh@informatik.uni-kiel.de>
Cc: shemminger@vyatta.com, error27@gmail.com, arnd@arndb.de,
jj@chaosbits.net, joe@perches.com, eric.dumazet@gmail.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: bcm: fixed coding style issues
Date: Mon, 31 Jan 2011 18:42:49 -0800 [thread overview]
Message-ID: <20110201024249.GB2634@suse.de> (raw)
In-Reply-To: <1296525024-21898-1-git-send-email-tvh@informatik.uni-kiel.de>
On Tue, Feb 01, 2011 at 02:50:24AM +0100, Timo von Holtz wrote:
> Fixed some coding style issues
Which ones?
With such a huge patch, it's best to break it down by type of coding
style cleanup, to make it easier to review and apply. This is almost
too big to review as-is :(
thanks,
greg k-h
next parent reply other threads:[~2011-02-01 2:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1296525024-21898-1-git-send-email-tvh@informatik.uni-kiel.de>
2011-02-01 2:42 ` Greg KH [this message]
2011-02-01 3:58 ` [PATCH] Staging: bcm: fixed coding style issues Stephen Hemminger
2011-02-01 5:33 ` Dan Carpenter
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=20110201024249.GB2634@suse.de \
--to=gregkh@suse.de \
--cc=arnd@arndb.de \
--cc=devel@driverdev.osuosl.org \
--cc=eric.dumazet@gmail.com \
--cc=error27@gmail.com \
--cc=jj@chaosbits.net \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shemminger@vyatta.com \
--cc=tvh@informatik.uni-kiel.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