From: David Miller <davem@davemloft.net>
To: skinsbursky@parallels.com
Cc: sim@hostway.ca, eric.dumazet@gmail.com, netdev@vger.kernel.org
Subject: Re: 3.3.0, 3.4-rc1 reproducible tun Oops
Date: Tue, 17 Apr 2012 22:38:50 -0400 (EDT) [thread overview]
Message-ID: <20120417.223850.1985192910706420371.davem@davemloft.net> (raw)
In-Reply-To: <4F8DBB22.7060302@parallels.com>
From: Stanislav Kinsbursky <skinsbursky@parallels.com>
Date: Tue, 17 Apr 2012 22:49:06 +0400
> Sorry for whitespaces.
> And thanks, Simon.
Please submit this fix formally, with Simon's Tested-by:
next prev parent reply other threads:[~2012-04-18 2:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 22:05 3.3.0, 3.4-rc1 reproducible tun Oops Simon Kirby
2012-04-05 2:41 ` Eric Dumazet
2012-04-05 5:58 ` Simon Kirby
2012-04-17 2:08 ` Simon Kirby
2012-04-17 12:18 ` Stanislav Kinsbursky
2012-04-17 18:35 ` Simon Kirby
2012-04-17 18:49 ` Stanislav Kinsbursky
2012-04-18 2:38 ` David Miller [this message]
2012-04-18 11:32 ` Stanislav Kinsbursky
2012-05-19 1:07 ` Simon Kirby
2012-05-21 14:51 ` Stanislav Kinsbursky
2012-04-18 6:51 Stanislav Kinsbursky
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=20120417.223850.1985192910706420371.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sim@hostway.ca \
--cc=skinsbursky@parallels.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).