From: Harvey Harrison <harvey.harrison@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: Commit c4438fa71bf412862ed0b73111956b0ffd8209d3 breaks WPA
Date: Tue, 01 Jul 2008 14:14:00 -0700 [thread overview]
Message-ID: <1214946840.24353.3.camel@brick> (raw)
In-Reply-To: <20080701203658.GA9225@tuxdriver.com>
On Tue, 2008-07-01 at 16:36 -0400, John W. Linville wrote:
> On Tue, Jul 01, 2008 at 03:23:36PM -0500, Larry Finger wrote:
> > 7fa906d1d2acc6f9d88b923eed0990b9b14ea830 M net
> >
> > This commit was confirmed as the problem by reverting it.
>
> Luckily that is just in my "pending" stack. I'll revert it ASAP.
> Harvey, you are welcome to resubmit if you can tell us what broke
> things! :-)
>
Will investigate it this evening.
Harvey
prev parent reply other threads:[~2008-07-01 21:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 20:23 Commit c4438fa71bf412862ed0b73111956b0ffd8209d3 breaks WPA Larry Finger
2008-07-01 20:36 ` John W. Linville
2008-07-01 21:14 ` Harvey Harrison [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=1214946840.24353.3.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).