linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave <kilroyd@googlemail.com>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: Pavel Roskin <proski@gnu.org>,
	orinoco-devel@lists.sourceforge.net,
	linux-wireless@vger.kernel.org
Subject: Re: [Orinoco-devel] [PATCH] orinoco: checkpatch cleanup take 2
Date: Tue, 27 Jan 2009 19:02:33 +0000	[thread overview]
Message-ID: <497F5A49.50507@gmail.com> (raw)
In-Reply-To: <200901260754.58084.arvidjaar@mail.ru>

Andrey Borzenkov wrote:
> On 26 ?????? 2009 06:46:02 Pavel Roskin wrote:
>> Please run the patch itself through checkpatch.  It finds two errors:
>>
>> ERROR: trailing statements should be on next line
>> #163: FILE: drivers/net/wireless/orinoco/hermes.c:65:
>> +                       printk(stuff); } while (0)
>> +                       printk(stuff); } while (0)
>> ERROR: do not use assignment in if condition
>> #698: FILE: drivers/net/wireless/orinoco/orinoco_cs.c:167:
>> +       if ((last_ret = (ret)) != 0) \
>>
>> total: 2 errors, 0 warnings, 786 lines checked
> 
> Thank you. Modified patch attached, now without errors.

Reviewed-by: David Kilroy <kilroyd@googlemail.com>

As far as I can tell, all the changes address a checkpatch warning, and
shouldn't modify behaviour of the code.

I specifically took a close look at the HERMES_BYTES_TO_RECLEN,
HERMES_RECLEN_TO_BYTES, CS_CHECK macros since they have potential to
hose the drivers. Looked OK to me.


Thanks,

Dave.

      reply	other threads:[~2009-01-27 19:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-25 19:54 [PATCH] orinoco: checkpatch cleanup Andrey Borzenkov
2009-01-25 19:59 ` Johannes Berg
2009-01-25 20:08   ` Andrey Borzenkov
2009-01-26  3:46     ` [Orinoco-devel] " Pavel Roskin
2009-01-26  4:54       ` [PATCH] orinoco: checkpatch cleanup take 2 Andrey Borzenkov
2009-01-27 19:02         ` Dave [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=497F5A49.50507@gmail.com \
    --to=kilroyd@googlemail.com \
    --cc=arvidjaar@mail.ru \
    --cc=linux-wireless@vger.kernel.org \
    --cc=orinoco-devel@lists.sourceforge.net \
    --cc=proski@gnu.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).