All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Bing Zhao <bzhao@marvell.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"kernel-janitors@vger.kernel.org"
	<kernel-janitors@vger.kernel.org>
Subject: Re: [patch] mwifiex: potential integer underflow in mwifiex_ret_wmm_get_status()
Date: Thu, 10 Oct 2013 17:26:33 +0000	[thread overview]
Message-ID: <20131010172633.GC2691@tuxdriver.com> (raw)
In-Reply-To: <477F20668A386D41ADCC57781B1F70430F4507819C@SC-VEXCH1.marvell.com>

On Thu, Sep 26, 2013 at 02:57:21PM -0700, Bing Zhao wrote:
> Hi Dan,
> 
> > There are several other similar functions as well.  For example, the
> > while loops in mwifiex_ret_tx_rate_cfg() and mwifiex_get_power_level().
> 
> Thanks for pointing it out. We will have them fixed.
> 
> Regards,
> Bing

OK, I'm confused by this thread...I'm dropping it.

Dan & Bing,

Please repost as a series of patches that I don't have to piece
together from a series of replies...

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

WARNING: multiple messages have this Message-ID (diff)
From: "John W. Linville" <linville@tuxdriver.com>
To: Bing Zhao <bzhao@marvell.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"kernel-janitors@vger.kernel.org"
	<kernel-janitors@vger.kernel.org>
Subject: Re: [patch] mwifiex: potential integer underflow in mwifiex_ret_wmm_get_status()
Date: Thu, 10 Oct 2013 13:26:33 -0400	[thread overview]
Message-ID: <20131010172633.GC2691@tuxdriver.com> (raw)
In-Reply-To: <477F20668A386D41ADCC57781B1F70430F4507819C@SC-VEXCH1.marvell.com>

On Thu, Sep 26, 2013 at 02:57:21PM -0700, Bing Zhao wrote:
> Hi Dan,
> 
> > There are several other similar functions as well.  For example, the
> > while loops in mwifiex_ret_tx_rate_cfg() and mwifiex_get_power_level().
> 
> Thanks for pointing it out. We will have them fixed.
> 
> Regards,
> Bing

OK, I'm confused by this thread...I'm dropping it.

Dan & Bing,

Please repost as a series of patches that I don't have to piece
together from a series of replies...

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2013-10-10 17:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-25  8:57 [patch] mwifiex: potential integer underflow in mwifiex_ret_wmm_get_status() Dan Carpenter
2013-09-25  8:57 ` Dan Carpenter
2013-09-25 16:25 ` Bing Zhao
2013-09-25 16:25   ` Bing Zhao
2013-09-25 18:23   ` Dan Carpenter
2013-09-25 18:23     ` Dan Carpenter
2013-09-25 23:10     ` Bing Zhao
2013-09-25 23:10       ` Bing Zhao
2013-09-26 20:57       ` Bing Zhao
2013-09-26 20:57         ` Bing Zhao
2013-09-26 21:07         ` Dan Carpenter
2013-09-26 21:07           ` Dan Carpenter
2013-09-26 21:57           ` Bing Zhao
2013-09-26 21:57             ` Bing Zhao
2013-10-10 17:26             ` John W. Linville [this message]
2013-10-10 17:26               ` John W. Linville
2013-10-10 18:02               ` Bing Zhao
2013-10-10 18:02                 ` Bing Zhao

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=20131010172633.GC2691@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=bzhao@marvell.com \
    --cc=dan.carpenter@oracle.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-wireless@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.