From: "J. C. Jones" <jaibuduvin@gmail.com>
To: <linux-wireless@vger.kernel.org>
Subject: Which Mailing List Should I Use?
Date: Thu, 23 Aug 2012 22:59:19 -0500 [thread overview]
Message-ID: <004501cd81ac$d766f7e0$8634e7a0$@com> (raw)
In-Reply-To: <477F20668A386D41ADCC57781B1F7043083B0BBB71@SC-VEXCH1.marvell.com>
Hi All,
I sent a message to ath9k-devel@lists.ath9k.org a few days ago (fragment of
message below), and it was rejected multiple times. I have not received any
messages from that list since.
Did I miss anything?
Best Regards,
-JC
Delivery to the following recipient failed permanently:
ath9k-devel@lists.ath9k.org
Technical details of permanent failure:
The recipient server did not accept our requests to connect. Learn more at
http://support.google.com/mail/bin/answer.py?answer=7720
[(0) lists.ath9k.org. [194.45.26.84]:25: Connection refused]
next prev parent reply other threads:[~2012-08-24 3:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 2:56 [PATCH] mwifiex: use is_zero_ether_addr() instead of memcmp() Wei Yongjun
2012-08-24 3:30 ` Bing Zhao
2012-08-24 3:59 ` J. C. Jones [this message]
2012-08-24 4:03 ` Which Mailing List Should I Use? Pavel Roskin
2012-08-24 4:35 ` J. C. Jones
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='004501cd81ac$d766f7e0$8634e7a0$@com' \
--to=jaibuduvin@gmail.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 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).