From: John W. Linville <linville@tuxdriver.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH] ath9k: Fix read buffer overflow
Date: Mon, 10 Aug 2009 16:26:22 -0400 [thread overview]
Message-ID: <20090810202622.GB6060@tuxdriver.com> (raw)
In-Reply-To: <4A7CA188.1070706@gmail.com>
On Fri, Aug 07, 2009 at 11:50:00PM +0200, Roel Kluin wrote:
> Prevent a read of powInfo[-1] in the first iteration.
>
> Signed-off-by: Roel Kluin <roel.kluin@gmail.com>
> ---
> The last hunk I already sent in a previous patch.
The last two hunks, apparently -- neither of them apply.
Why on earth would you randomly include those hunks here? Especially
if you already sent them?
Listen, I'm glad you are there to do these various clean-ups.
But honestly your patches seem to always have some problem that
requires manual intervention to apply them. You make my life hard,
and you slow me down. That makes John a grumpy boy.
John
--
John W. Linville Someday the world will need a hero, and you
linville at 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: Roel Kluin <roel.kluin@gmail.com>
Cc: Jouni Malinen <jmalinen@atheros.com>,
linux-wireless@vger.kernel.org, ath9k-devel@lists.ath9k.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] ath9k: Fix read buffer overflow
Date: Mon, 10 Aug 2009 16:26:22 -0400 [thread overview]
Message-ID: <20090810202622.GB6060@tuxdriver.com> (raw)
In-Reply-To: <4A7CA188.1070706@gmail.com>
On Fri, Aug 07, 2009 at 11:50:00PM +0200, Roel Kluin wrote:
> Prevent a read of powInfo[-1] in the first iteration.
>
> Signed-off-by: Roel Kluin <roel.kluin@gmail.com>
> ---
> The last hunk I already sent in a previous patch.
The last two hunks, apparently -- neither of them apply.
Why on earth would you randomly include those hunks here? Especially
if you already sent them?
Listen, I'm glad you are there to do these various clean-ups.
But honestly your patches seem to always have some problem that
requires manual intervention to apply them. You make my life hard,
and you slow me down. That makes John a grumpy boy.
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2009-08-10 20:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 21:50 [ath9k-devel] [PATCH] ath9k: Fix read buffer overflow Roel Kluin
2009-08-07 21:50 ` Roel Kluin
2009-08-10 20:26 ` John W. Linville [this message]
2009-08-10 20:26 ` John W. Linville
2009-08-11 6:49 ` [ath9k-devel] " Roel Kluin
2009-08-11 6:49 ` Roel Kluin
2009-08-11 18:25 ` [ath9k-devel] " John W. Linville
2009-08-11 18:25 ` John W. Linville
2009-08-20 14:52 ` [ath9k-devel] " John W. Linville
2009-08-20 14:52 ` John W. Linville
2009-08-24 23:34 ` [ath9k-devel] " Luis R. Rodriguez
2009-08-24 23:34 ` Luis R. Rodriguez
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=20090810202622.GB6060@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=ath9k-devel@lists.ath9k.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.