From: Fabio Rossi <rossi.f@inwind.it>
To: Pavel Roskin <proski@gnu.org>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: p54: ad-hoc mode doesn't work
Date: Mon, 29 Dec 2008 20:38:31 +0100 [thread overview]
Message-ID: <200812292038.31777.rossi.f@inwind.it> (raw)
In-Reply-To: <20081224171050.uk6j9x861c8g0o0w-cebfxv@webmail.spamcop.net>
On Wednesday 24 December 2008, Pavel Roskin wrote:
> Perhaps we need a separate error code "not permitted by regulations".
> Or we need to reuse one of the existing error codes for that.
Yes, this would be better for the end-user.
Fabio
prev parent reply other threads:[~2008-12-29 19:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-23 0:32 p54: ad-hoc mode doesn't work Fabio Rossi
2008-12-23 22:52 ` Pavel Roskin
2008-12-24 17:28 ` Fabio Rossi
2008-12-24 17:37 ` Pavel Roskin
2008-12-24 21:03 ` Fabio Rossi
2008-12-24 17:40 ` Luis R. Rodriguez
2008-12-24 21:03 ` Fabio Rossi
2008-12-24 22:10 ` Pavel Roskin
2008-12-29 19:38 ` Fabio Rossi [this message]
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=200812292038.31777.rossi.f@inwind.it \
--to=rossi.f@inwind.it \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=proski@gnu.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).