From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Michael Sprecher <sprecher.m@gmail.com>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
Jouni Malinen <Jouni.Malinen@Atheros.com>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH] wireless: ath9k: Fix most coding style issues in ath9k This patch fixed up almost all coding style issues in the ath9k driver found by the ceckpatch.pl tool. Signed-off-by: Michael Sprecher <sprecher.m@gmail.com>
Date: Tue, 27 Apr 2010 14:05:24 -0700 [thread overview]
Message-ID: <20100427210524.GD9046@tux> (raw)
In-Reply-To: <s2yf42143521004271321qe6522fdaia42f335575d4026@mail.gmail.com>
On Tue, Apr 27, 2010 at 01:21:21PM -0700, Michael Sprecher wrote:
> Yes, i'm still intrested in fixing your coding style issues ;)
> If it's now safe to check it again, i will find some time to look at it this week.
> Michael
Go for it, after John merges our latest batch you should be good to go
Luis
prev parent reply other threads:[~2010-04-27 21:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 19:05 [PATCH] wireless: ath9k: Fix most coding style issues in ath9k This patch fixed up almost all coding style issues in the ath9k driver found by the ceckpatch.pl tool. Signed-off-by: Michael Sprecher <sprecher.m@gmail.com> Michael Sprecher
2010-03-09 19:33 ` Luis R. Rodriguez
2010-04-08 18:41 ` John W. Linville
2010-04-08 19:12 ` Luis R. Rodriguez
[not found] ` <h2xf42143521004271314rb3a000arba8f9df5846e71ab@mail.gmail.com>
[not found] ` <j2of42143521004271315ice41b0edtabf0ed4914342d41@mail.gmail.com>
[not found] ` <s2yf42143521004271321qe6522fdaia42f335575d4026@mail.gmail.com>
2010-04-27 21:05 ` Luis R. Rodriguez [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=20100427210524.GD9046@tux \
--to=lrodriguez@atheros.com \
--cc=Jouni.Malinen@Atheros.com \
--cc=Luis.Rodriguez@Atheros.com \
--cc=ath9k-devel@lists.ath9k.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=sprecher.m@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).