linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave <kilroyd@googlemail.com>
To: Pavel Roskin <proski@gnu.org>
Cc: John W Linville <linville@tuxdriver.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] orinoco: fix last beacon reporting on 64-bit systems
Date: Wed, 12 Nov 2008 00:48:52 +0000	[thread overview]
Message-ID: <491A27F4.7070400@gmail.com> (raw)
In-Reply-To: <20081110142553.12216.42412.stgit@dv.roinet.com>

Pavel Roskin wrote:
> orinoco_translate_scan() and orinoco_translate_ext_scan() wrongly
> truncate last_scanned argument from unsigned long to unsigned int.
> 
> Signed-off-by: Pavel Roskin <proski@gnu.org>

Well spotted. IIRC that was the one of the issues you noticed with scan
output when testing my WPA patch series.

ACK from me, if it matters.


Dave.

      reply	other threads:[~2008-11-12  0:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-10 14:25 [PATCH] orinoco: fix last beacon reporting on 64-bit systems Pavel Roskin
2008-11-12  0:48 ` Dave [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=491A27F4.7070400@gmail.com \
    --to=kilroyd@googlemail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).