From: Pegasus11 <aijazbaig1.new@gmail.com>
To: linuxppc-dev@ozlabs.org
Subject: Re: Understanding how kernel updates MMU hash table
Date: Tue, 11 Dec 2012 21:10:47 -0800 (PST) [thread overview]
Message-ID: <34786958.post@talk.nabble.com> (raw)
In-Reply-To: <34760537.post@talk.nabble.com>
I cannot see my post at all on the old nabble system...this is just for
testing purposes//...
My last post is fine..but I cannot see my thread on linuxppc-dev@oldnabble
...?? :confused:
--
View this message in context: http://old.nabble.com/Understanding-how-kernel-updates-MMU-hash-table-tp34760537p34786958.html
Sent from the linuxppc-dev mailing list archive at Nabble.com.
prev parent reply other threads:[~2012-12-12 5:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 5:56 Understanding how kernel updates MMU hash table Pegasus11
2012-12-05 8:20 ` Benjamin Herrenschmidt
2012-12-05 17:14 ` Pegasus11
2012-12-06 3:58 ` Benjamin Herrenschmidt
2012-12-06 7:57 ` Pegasus11
2012-12-06 11:56 ` Benjamin Herrenschmidt
2012-12-09 7:18 ` Pegasus11
2012-12-09 21:10 ` Benjamin Herrenschmidt
2012-12-11 7:27 ` Pegasus11
2012-12-13 8:48 ` pegasus
2012-12-13 21:48 ` Benjamin Herrenschmidt
2012-12-12 5:10 ` Pegasus11 [this message]
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=34786958.post@talk.nabble.com \
--to=aijazbaig1.new@gmail.com \
--cc=linuxppc-dev@ozlabs.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).