From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Luis de Bethencourt <luisbg@ubuntu.com>
Cc: "linville@tuxdriver.com" <linville@tuxdriver.com>,
Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] ath: fix code readability in regd.c
Date: Tue, 30 Mar 2010 09:56:45 -0700 [thread overview]
Message-ID: <20100330165645.GB25095@tux> (raw)
In-Reply-To: <1269963873-2070-1-git-send-email-luisbg@ubuntu.com>
On Tue, Mar 30, 2010 at 08:44:33AM -0700, Luis de Bethencourt wrote:
> This is a patch to the ath/regd.c file that fixes two code
> readability issues. A space between to separate two defines
> and the indentation inside the ath_redg_is_eeprom_valid
> function.
Acked-by: Luis R. Rodriguez <lrodriguez@atheros.com>
You can drop netdev and linux-kernel from future linux-wireless e-mails
like this one.
Luis
next prev parent reply other threads:[~2010-03-30 16:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ath/regd.c>
2010-03-30 15:44 ` [PATCH 2/2] ath: fix code readability in regd.c Luis de Bethencourt
2010-03-30 16:56 ` Luis R. Rodriguez [this message]
2010-03-30 17:08 ` Luis de Bethencourt
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=20100330165645.GB25095@tux \
--to=lrodriguez@atheros.com \
--cc=Luis.Rodriguez@Atheros.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=luisbg@ubuntu.com \
--cc=netdev@vger.kernel.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