From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Joe Perches <joe@perches.com>
Cc: <devel@linuxdriverproject.org>, <gregkh@suse.de>,
<error27@gmail.com>, <linux-kernel@vger.kernel.org>,
<linux-wireless@vger.kernel.org>, <netdev@vger.kernel.org>
Subject: Re: [PATCH 0/2] ath6kl: more neatening
Date: Mon, 18 Jul 2011 00:49:43 +0300 [thread overview]
Message-ID: <4E2358F7.3020709@qca.qualcomm.com> (raw)
In-Reply-To: <cover.1310938421.git.joe@perches.com>
On 07/18/2011 12:38 AM, Joe Perches wrote:
>> Great, thanks. I have now applied your patches to ath6kl-cleanup tree
>> and they will be included in patchset v3.
>
> Here's a couple of more.
>
> Joe Perches (2):
> ath6kl: Remove __func__ uses from ath6kl_dbg
> ath6kl: Remove trailing unpaired close paren from ath6kl_err uses
Thanks again.
I just sent v3. But if I need to create v4 (I hope not) I'll include
your patches. If v3 is ok, I can resend your patches to wireless-testing
so that you don't need to followup.
Kalle
next prev parent reply other threads:[~2011-07-17 21:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-17 18:43 [PATCH 0/3] ath6kl: neatening Joe Perches
2011-07-17 18:43 ` [PATCH 1/3] ath6kl: Add missing newlines and coalesce messages Joe Perches
2011-07-17 18:43 ` [PATCH 2/3] ath6kl: Remove __func__ uses from ath6kl_err Joe Perches
2011-07-17 18:43 ` [PATCH 3/3] ath6kl: cfg80211: Add and use ath6kl_cfg80211_ready helper Joe Perches
2011-07-17 18:56 ` [PATCH 0/3] ath6kl: neatening Kalle Valo
2011-07-17 19:52 ` Joe Perches
2011-07-17 20:45 ` Kalle Valo
2011-07-17 21:38 ` [PATCH 0/2] ath6kl: more neatening Joe Perches
2011-07-17 21:38 ` [PATCH 1/2] ath6kl: Remove __func__ uses from ath6kl_dbg Joe Perches
2011-07-17 21:49 ` Kalle Valo [this message]
[not found] ` <4E2349D4.4000204-A+ZNKFmMK5xy9aJCnZT0Uw@public.gmane.org>
[not found] ` <cover.1310938421.git.joe-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
2011-07-17 21:38 ` [PATCH 2/2] ath6kl: Remove trailing unpaired close paren from ath6kl_err uses Joe Perches
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=4E2358F7.3020709@qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=devel@linuxdriverproject.org \
--cc=error27@gmail.com \
--cc=gregkh@suse.de \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).