From: Zhu Yi <yi.zhu@intel.com>
To: Adrian Bunk <bunk@kernel.org>,
"John W.Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org,
ipw3945-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] iwl4965-base.c: fix off-by-one errors
Date: Wed, 17 Oct 2007 15:33:52 +0800 [thread overview]
Message-ID: <1192606433.2992.20.camel@debian.sh.intel.com> (raw)
In-Reply-To: <20071014175115.GL4211@stusta.de>
On Sun, 2007-10-14 at 19:51 +0200, Adrian Bunk wrote:
> This patch fixes two off-by-one errors resulting in array overflows
> spotted by the Coverity checker.
>
> Signed-off-by: Adrian Bunk <bunk@kernel.org>
ACK.
John, please apply.
Thanks,
-yi
next prev parent reply other threads:[~2007-10-17 7:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-14 17:51 [2.6 patch] iwl4965-base.c: fix off-by-one errors Adrian Bunk
2007-10-17 7:33 ` Zhu Yi [this message]
2007-10-18 14:35 ` Cahill, Ben M
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=1192606433.2992.20.camel@debian.sh.intel.com \
--to=yi.zhu@intel.com \
--cc=bunk@kernel.org \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--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).