From: Bastian Bittorf <bittorf@bluebottle.com>
To: Ben Greear <greearb@candelatech.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
ath10k <ath10k@lists.infradead.org>
Subject: Re: No more posts about ath10k CT firmware for a while.
Date: Wed, 30 Sep 2015 21:12:25 +0200 [thread overview]
Message-ID: <20150930191225.GY22537@medion.lan> (raw)
In-Reply-To: <560C3051.10702@candelatech.com>
* Ben Greear <greearb@candelatech.com> [30.09.2015 21:08]:
> I've been asked to not post any ath10k CT firmware related info
this makes me sad, because it is related.
whoever asked you, can she/he stand up and explain?
bye, bastian
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Bastian Bittorf <bittorf@bluebottle.com>
To: Ben Greear <greearb@candelatech.com>
Cc: ath10k <ath10k@lists.infradead.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: No more posts about ath10k CT firmware for a while.
Date: Wed, 30 Sep 2015 21:12:25 +0200 [thread overview]
Message-ID: <20150930191225.GY22537@medion.lan> (raw)
In-Reply-To: <560C3051.10702@candelatech.com>
* Ben Greear <greearb@candelatech.com> [30.09.2015 21:08]:
> I've been asked to not post any ath10k CT firmware related info
this makes me sad, because it is related.
whoever asked you, can she/he stand up and explain?
bye, bastian
next prev parent reply other threads:[~2015-09-30 19:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 18:56 No more posts about ath10k CT firmware for a while Ben Greear
2015-09-30 18:56 ` Ben Greear
2015-09-30 19:12 ` Bastian Bittorf [this message]
2015-09-30 19:12 ` Bastian Bittorf
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=20150930191225.GY22537@medion.lan \
--to=bittorf@bluebottle.com \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.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.