LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: unlisted-recipients:; (no To-header on input)
Cc: Paul Moore <paul.moore@hp.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: 2.6.24-rc6-mm1 - oddness with IPv4/v6 mapped sockets hanging...
Date: Mon, 14 Jan 2008 13:22:10 -0500 [thread overview]
Message-ID: <32065.1200334930@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 14 Jan 2008 13:05:48 EST." <31130.1200333948@turing-police.cc.vt.edu>
[-- Attachment #1: Type: text/plain, Size: 472 bytes --]
On Mon, 14 Jan 2008 13:05:48 EST, Valdis.Kletnieks@vt.edu said:
> I'm pulling git://git.infradead.org/users/pcmoore/lblnet-2.6_testing at the
> moment, and seeing if there's already a fix in there for this.
Apparently the only new commit in there since the tree that was in
24-rc6-mm1 is 5d95575903fd3865b884952bd93c339d48725c33 adding some warning
printk's. Would it be more productive to test against the full tree, or
leaving out the one commit I already reverted?
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2008-01-14 18:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-13 7:35 2.6.24-rc6-mm1 - oddness with IPv4/v6 mapped sockets hanging Valdis.Kletnieks
2008-01-13 21:46 ` Herbert Xu
2008-01-14 16:15 ` Valdis.Kletnieks
2008-01-14 16:36 ` Paul Moore
2008-01-14 18:05 ` Valdis.Kletnieks
2008-01-14 18:22 ` Valdis.Kletnieks [this message]
2008-01-14 18:50 ` Valdis.Kletnieks
2008-01-14 19:07 ` Paul Moore
2008-01-14 19:37 ` Valdis.Kletnieks
2008-01-14 20:02 ` Paul Moore
2008-01-14 23:04 ` Valdis.Kletnieks
2008-01-14 23:19 ` Paul Moore
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=32065.1200334930@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul.moore@hp.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).