linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Mark Hagger <mark.hagger@m-spatial.com>
Cc: John Linville <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org, bcm43xx-dev@lists.berlios.de
Subject: Re: [PATCH] b43: Enable quantum cryptography support
Date: Tue, 1 Apr 2008 17:14:22 +0200	[thread overview]
Message-ID: <200804011714.22378.mb@bu3sch.de> (raw)
In-Reply-To: <1207061419.2879.298.camel@giga.cambridge.m-spatial.com>

On Tuesday 01 April 2008 16:50:19 Mark Hagger wrote:
> Excellent, did you manage to implement the time travel support mode as
> well?

Sure. I used it to actually get one of those q-crypto devices to test
the code. ;)

-- 
Greetings Michael.

  parent reply	other threads:[~2008-04-01 15:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-01 14:13 [PATCH] b43: Enable quantum cryptography support Michael Buesch
2008-04-01 14:50 ` Mark Hagger
2008-04-01 14:56   ` Ivo van Doorn
2008-04-01 15:14   ` Michael Buesch [this message]
2008-04-01 17:34 ` gavron
2008-04-01 17:48   ` Stefanik Gábor

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=200804011714.22378.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mark.hagger@m-spatial.com \
    /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).