linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Miles Lane <miles.lane@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	ath9k-devel@lists.ath9k.org,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [ath9k-devel] BUG kmalloc-8192: Poison overwritten
Date: Thu, 03 Dec 2009 21:22:28 -0800	[thread overview]
Message-ID: <4B189C94.4080404@gmail.com> (raw)
In-Reply-To: <43e72e890912031345m3f5adb9nca754e33a858c923@mail.gmail.com>

On 12/03/09 13:45, Luis R. Rodriguez wrote:


> I think waiting to be able to reproduce is best, and appreciate your
> patience on this. Maybe Miles Lanes also cannot reproduce easily and
> that may explain why he hasn't replied.
>
>    Luis
>

o.k., did some more experimenting
but came up with something other than
what I was hoping for(something with s2ram),
Anyways the two patches applied clean,
I'll just run  the system with these in,
and if somebody comes along with more expertise
on this I can try their advice(or if I somehow find
a way to reproduce this).

Justin P. Mattock

      parent reply	other threads:[~2009-12-04  5:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <dd18b0c30912021427x4d1d952tcdd98bb9d816b67c@mail.gmail.com>
     [not found] ` <43e72e890912021516k736db118j217dc92496db8f19@mail.gmail.com>
     [not found]   ` <4B182F79.7060103@gmail.com>
2009-12-03 21:45     ` [ath9k-devel] BUG kmalloc-8192: Poison overwritten Luis R. Rodriguez
2009-12-03 21:58       ` Justin P. Mattock
2009-12-04  5:22       ` Justin P. Mattock [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=4B189C94.4080404@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=ath9k-devel@lists.ath9k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    --cc=miles.lane@gmail.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).