netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Drake <dsd@gentoo.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Laurent Riffard <laurent.riffard@free.fr>,
	linville@tuxdriver.com, netdev@vger.kernel.org
Subject: Re: [PATCH] sotftmac: fix a slab corruption in WEP restricted key association
Date: Fri, 13 Oct 2006 08:08:37 -0400	[thread overview]
Message-ID: <452F81C5.9000801@gentoo.org> (raw)
In-Reply-To: <1160730291.2697.10.camel@ux156>

Johannes Berg wrote:
> Good catch. We should send this to -stable too I think. Mind reposting
> the patch in an applicable format to Daniel, netdev, john, -stable (and
> possibly me)? Quoted isn't too useful :)

It was already sent to John directly. I was planning on sending it to 
-stable as soon as it hits Linus' tree.

Daniel


  reply	other threads:[~2006-10-13 12:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <452D6D80.3020005@free.fr>
2006-10-12  0:34 ` [PATCH] sotftmac: fix a slab corruption in WEP restricted key association Daniel Drake
2006-10-13  9:04   ` Johannes Berg
2006-10-13 12:08     ` Daniel Drake [this message]
2006-10-13 12:12       ` Johannes Berg

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=452F81C5.9000801@gentoo.org \
    --to=dsd@gentoo.org \
    --cc=johannes@sipsolutions.net \
    --cc=laurent.riffard@free.fr \
    --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 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).