From: Pavel Roskin <proski@gnu.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: netdev@vger.kernel.org, hostap@shmoo.com
Subject: Re: [PATCH] hostap_plx: fix CIS verification
Date: Tue, 24 Oct 2006 20:48:09 -0400 [thread overview]
Message-ID: <1161737289.29298.6.camel@dv> (raw)
In-Reply-To: <20061025003707.GB7340@tuxdriver.com>
On Tue, 2006-10-24 at 20:37 -0400, John W. Linville wrote:
> Will you be refactoring this patch? Or do you disagree with Jouni's
> assessment?
OK, give me an hour to produce a better patch. My patch has an
advantage of being simple and of fixing exactly one thing, but if Jouni
feels more comfortable with an additional check, I'll add it.
I don't have Coverity to check, and I think the results of Coverity were
misinterpreted. It doesn't know anything about CIS structure. Anyway,
let me just check Jouni's suggestion on a real PLX card.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2006-10-25 0:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 22:20 [PATCH] hostap_plx: fix CIS verification Pavel Roskin
2006-10-21 1:19 ` Jouni Malinen
2006-10-25 0:37 ` John W. Linville
2006-10-25 0:48 ` Pavel Roskin [this message]
2006-10-25 1:44 ` Jouni Malinen
2006-10-25 2:12 ` Pavel Roskin
2006-10-25 2:31 ` Jouni Malinen
2006-10-25 2:41 ` [PATCH FIXED] " Pavel Roskin
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=1161737289.29298.6.camel@dv \
--to=proski@gnu.org \
--cc=hostap@shmoo.com \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.