netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: netdev@vger.kernel.org, hostap@shmoo.com, Pavel Roskin <proski@gnu.org>
Subject: Re: [PATCH] Fix crash on big-endian systems during scan
Date: Mon, 17 Apr 2006 10:34:03 -0400	[thread overview]
Message-ID: <1145284443.2212.5.camel@localhost.localdomain> (raw)
In-Reply-To: <20060417132105.GF5042@tuxdriver.com>

On Mon, 2006-04-17 at 09:21 -0400, John W. Linville wrote:
> On Sun, Apr 16, 2006 at 06:06:02PM -0700, Jouni Malinen wrote:
> > On Fri, Apr 14, 2006 at 05:59:11PM -0400, Pavel Roskin wrote:
> > 
> > > The original code was doing arithmetics on a little-endian value.
> > 
> > John, please apply this to wireless-2.6 tree. This code is triggered at
> > least for the case where WPA is not used. I had noticed it before, but I
> > think I've only tested WPA/WPA2 on big endian systems..
> 
> Can someone repost this patch?  I seem to have missed it.

Pavel posted to netdev originally on Friday April 14th with the patch
included in the email, with the title "[PATCH] Fix crash on big-endian
systems during scan"...

http://www.spinics.net/lists/netdev/msg03023.html

Sure you don't have it somewhere?  If not, I'm sure somebody can
resend...

Dan



  reply	other threads:[~2006-04-17 14:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-14 21:59 [PATCH] Fix crash on big-endian systems during scan Pavel Roskin
2006-04-17  1:06 ` Jouni Malinen
2006-04-17 13:21   ` John W. Linville
2006-04-17 14:34     ` Dan Williams [this message]
2006-04-17 14:45       ` John W. Linville
2006-04-17 15:01         ` Dan Williams
2006-04-17 15:17           ` John W. Linville
2006-04-17 15:36             ` Dan Williams
2006-04-17 16:44               ` John W. Linville

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=1145284443.2212.5.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=hostap@shmoo.com \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.org \
    --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).