All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: John Daiker <daikerjohn@gmail.com>
Cc: rt2400-devel@lists.sourceforge.net,
	linux-wireless@vger.kernel.org,
	"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH] rt2x00: reduce checkpatch.pl errors
Date: Fri, 17 Oct 2008 21:27:03 +0200	[thread overview]
Message-ID: <200810172127.04168.IvDoorn@gmail.com> (raw)
In-Reply-To: <48F8E481.7000308@gmail.com>

On Friday 17 October 2008, John Daiker wrote:
> A few changes to reduce checkpatch.pl errors in the rt2x00 driver.  For 
> the most part, I only fixed cosmetic things, and left the actual 'code 
> flow' untouched (hopefully)!
> 
> Diff is against wireless-testing HEAD.

Looks good. Thanks.

John could you merge this into wireless-testing? :)

> Signed-off-by: John Daiker <daikerjohn@gmail.com>

Signed-off-by: Ivo van Doorn <IvDoorn@gmail.com>

      reply	other threads:[~2008-10-17 19:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-17 19:16 [PATCH] rt2x00: reduce checkpatch.pl errors John Daiker
2008-10-17 19:27 ` Ivo van Doorn [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=200810172127.04168.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=daikerjohn@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=rt2400-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.