From: Hagen Paul Pfeifer <hagen@jauu.net>
To: Andreas Klauer <Andreas.Klauer@metamorpher.de>
Cc: netdev@vger.kernel.org
Subject: Re: 2.6.34 + IPv6: Oops?
Date: Mon, 21 Jun 2010 18:25:18 +0200 [thread overview]
Message-ID: <20100621162518.GA5972@nuttenaction> (raw)
In-Reply-To: <20100621153018.GA2433@EIS>
* Andreas Klauer | 2010-06-21 17:30:18 [+0200]:
>Hi,
>
>no one replied so far - am I reporting this to the wrong place?
>Please advise.
It is the right place, some guys are in holiday but probably you can git
bisect the problem?
HGN
next prev parent reply other threads:[~2010-06-21 16:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-19 17:53 2.6.34 + IPv6: Oops? Andreas Klauer
2010-06-21 15:30 ` Andreas Klauer
2010-06-21 16:19 ` Stephen Hemminger
2010-06-21 16:26 ` Andreas Klauer
2010-06-21 16:25 ` Hagen Paul Pfeifer [this message]
2010-06-21 17:25 ` Stephen Hemminger
2010-06-21 20:04 ` Andreas Klauer
2010-06-21 21:00 ` [PATCH] ipv6: fix NULL reference in proxy neighbor discovery Stephen Hemminger
2010-06-23 14:44 ` YOSHIFUJI Hideaki
2010-06-26 4:31 ` David Miller
2010-06-22 12:29 ` 2.6.34 + IPv6: Oops? Andreas Klauer
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=20100621162518.GA5972@nuttenaction \
--to=hagen@jauu.net \
--cc=Andreas.Klauer@metamorpher.de \
--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).