From: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
To: Zac Storer <zac.3.14159@gmail.com>
Cc: linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] Drivers: video: riva: riva_hw: fixed a brace coding
Date: Sun, 20 Nov 2011 01:50:33 +0000 [thread overview]
Message-ID: <4EC85CE9.6060706@gmx.de> (raw)
In-Reply-To: <1321591537-8475-1-git-send-email-zac.3.14159@gmail.com>
On 11/18/2011 04:45 AM, Zac Storer wrote:
> Fixed a brace coding style issue.
*sigh* You are fixing coding style, but I still get lots of warnings for the
single line you are changing. IF you are fixing coding style, at least do it
right. Or do you really expect me to be happy if you send me 3 patches that all
touch the same line?
Really, if you want to fix it, at least fix it in a way that checkpatch.pl does
no longer complain about your patch, at least regarding coding style issues. And
for such patches I think a per file patch or similar would be appropriate.
Regards,
Florian Tobias Schandinat
>
> Signed-off-by: Zac Storer <zac.3.14159@gmail.com>
> ---
> drivers/video/riva/riva_hw.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/video/riva/riva_hw.c b/drivers/video/riva/riva_hw.c
> index 78fdbf5..c4b8a6f 100644
> --- a/drivers/video/riva/riva_hw.c
> +++ b/drivers/video/riva/riva_hw.c
> @@ -994,7 +994,7 @@ static void nv10CalcArbitration
> clwm = clwm_mt;
> */
> /* Finally, a heuristic check when width = 64 bits */
> - if(width = 1){
> + if(width = 1) {
> nvclk_fill = nvclk_freq * 8;
> if(crtc_drain_rate * 100 >= nvclk_fill * 102)
> clwm = 0xfff; /*Large number to fail */
prev parent reply other threads:[~2011-11-20 1:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 4:45 [PATCH 5/5] Drivers: video: riva: riva_hw: fixed a brace coding style issue Zac Storer
2011-11-20 1:50 ` Florian Tobias Schandinat [this message]
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=4EC85CE9.6060706@gmx.de \
--to=florianschandinat@gmx.de \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zac.3.14159@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;
as well as URLs for NNTP newsgroup(s).