From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Pavel Roskin <proski@gnu.org>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] crda: prevent key2pub.py from generating bogus output on failure
Date: Fri, 9 Jan 2009 16:19:33 -0800 [thread overview]
Message-ID: <20090110001933.GL4416@tesla> (raw)
In-Reply-To: <20090110001852.GK4416@tesla>
On Fri, Jan 09, 2009 at 04:18:52PM -0800, Luis Rodriguez wrote:
> On Fri, Jan 09, 2009 at 04:16:50PM -0800, Pavel Roskin wrote:
> > Specify output file on the command line, so that it's not created in
> > case of fatal errors, such as asbence of M2Crypto.
> >
> > Signed-off-by: Pavel Roskin <proski@gnu.org>
>
> Thanks, BTW these should be addressed to John as its his tree.
Ooops wait sorry wrong tree -- heh.. I'll apply! The wireless-regdb is John's
tree though.
Thanks!
Luis
next prev parent reply other threads:[~2009-01-10 0:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-10 0:16 [PATCH] crda: prevent key2pub.py from generating bogus output on failure Pavel Roskin
2009-01-10 0:18 ` Luis R. Rodriguez
2009-01-10 0:19 ` Luis R. Rodriguez [this message]
2009-01-15 17:58 ` Luis R. Rodriguez
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=20090110001933.GL4416@tesla \
--to=lrodriguez@atheros.com \
--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).