From: "John W. Linville" <linville@tuxdriver.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: ath6kl-devel@qca.qualcomm.com, linux-wireless@vger.kernel.org,
ath10k@lists.infradead.org
Subject: Re: Pull request: ath-current 20130723
Date: Mon, 29 Jul 2013 14:42:03 -0400 [thread overview]
Message-ID: <20130729184203.GD31172@tuxdriver.com> (raw)
In-Reply-To: <87ehapwqum.fsf@kamboji.qca.qualcomm.com>
On Tue, Jul 23, 2013 at 12:46:57PM +0300, Kalle Valo wrote:
> Hi John,
>
> here's an ath6kl and ath10k pull request for 3.11-rc series.
>
> Geert Uytterhoeven fixed an ath10k build problem when NO_DMA=y. I added
> a missing MAINTAINERS entry for ath10k and updated ath6kl git tree
> location.
>
> Please let me know if there are any problems, or if you prefer me to
> send them through wireless-next instead.
>
> Kalle
>
> The following changes since commit 64b6f46f1141ad938e354f37af62e28da972e8eb:
>
> ath9k_hw: Fix multicast search for AR9002 family (2013-07-18 16:22:00 -0400)
>
> are available in the git repository at:
>
> git://github.com/kvalo/ath.git for-linville-current
>
> for you to fetch changes up to 58cfb681bffb43654776a218a087028ff425ba9e:
>
> MAINTAINERS: update ath6kl git location (2013-07-22 12:26:12 +0300)
Pulling now...
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: "John W. Linville" <linville@tuxdriver.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, ath6kl-devel@qca.qualcomm.com,
ath10k@lists.infradead.org
Subject: Re: Pull request: ath-current 20130723
Date: Mon, 29 Jul 2013 14:42:03 -0400 [thread overview]
Message-ID: <20130729184203.GD31172@tuxdriver.com> (raw)
In-Reply-To: <87ehapwqum.fsf@kamboji.qca.qualcomm.com>
On Tue, Jul 23, 2013 at 12:46:57PM +0300, Kalle Valo wrote:
> Hi John,
>
> here's an ath6kl and ath10k pull request for 3.11-rc series.
>
> Geert Uytterhoeven fixed an ath10k build problem when NO_DMA=y. I added
> a missing MAINTAINERS entry for ath10k and updated ath6kl git tree
> location.
>
> Please let me know if there are any problems, or if you prefer me to
> send them through wireless-next instead.
>
> Kalle
>
> The following changes since commit 64b6f46f1141ad938e354f37af62e28da972e8eb:
>
> ath9k_hw: Fix multicast search for AR9002 family (2013-07-18 16:22:00 -0400)
>
> are available in the git repository at:
>
> git://github.com/kvalo/ath.git for-linville-current
>
> for you to fetch changes up to 58cfb681bffb43654776a218a087028ff425ba9e:
>
> MAINTAINERS: update ath6kl git location (2013-07-22 12:26:12 +0300)
Pulling now...
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2013-07-29 18:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 9:46 Pull request: ath-current 20130723 Kalle Valo
2013-07-23 9:46 ` Kalle Valo
2013-07-29 18:42 ` John W. Linville [this message]
2013-07-29 18:42 ` John W. Linville
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=20130729184203.GD31172@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=ath10k@lists.infradead.org \
--cc=ath6kl-devel@qca.qualcomm.com \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@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 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.