From: Johannes Berg <johannes@sipsolutions.net>
To: deepak kumar Pradhan <hydipu@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Fwd: Linux kernel 3.12 PN-KEY Mismatch in wpa.c, packet drop
Date: Fri, 21 Nov 2014 16:19:43 +0100 [thread overview]
Message-ID: <1416583183.1881.10.camel@sipsolutions.net> (raw)
In-Reply-To: <CAGKQeFhjmo4LM9xTCSeuxu8R4VUwUSBiw-q9MaSiwB0eDpKBxg@mail.gmail.com> (sfid-20141121_161216_132074_564BF917)
On Fri, 2014-11-21 at 20:42 +0530, deepak kumar Pradhan wrote:
> Hi,
>
> Sorry for interrupting you.
> The below patch do recovers from pn-key mismatch in kernel 3.12 kernel
> packet drop issue.
> I don't know where I need to submit this patch for proper solution.
This is the right place for submitting a proper solution, but I believe
you've already been told that what you're doing isn't a proper solution
at all.
johannes
next prev parent reply other threads:[~2014-11-21 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 15:01 Linux kernel 3.12 PN-KEY Mismatch in wpa.c, packet drop deepak kumar Pradhan
2014-11-21 15:12 ` Fwd: " deepak kumar Pradhan
2014-11-21 15:19 ` Johannes Berg [this message]
2014-11-24 7:10 ` deepak kumar Pradhan
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=1416583183.1881.10.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=hydipu@gmail.com \
--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 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).