From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: David Rientjes <rientjes@google.com>
Cc: linux-arch@vger.kernel.org
Subject: Re: Link breakage on all architectures which implement their own show_mem
Date: Fri, 25 Mar 2011 09:13:41 -0500 [thread overview]
Message-ID: <1301062421.4073.3.camel@mulgrave.site> (raw)
In-Reply-To: <alpine.DEB.2.00.1103241520120.26730@chino.kir.corp.google.com>
On Thu, 2011-03-24 at 15:21 -0700, David Rientjes wrote:
> I don't have a parisc cross compiler, so if you could try it out and add
> your Tested-by that would be great
I'm afraid this hit at exactly the wrong time (we're relocating the
parisc dev cluster in cupertino), so all my parisc build systems are
currently trekking across country on fedex mules.
James
next prev parent reply other threads:[~2011-03-25 14:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 16:41 Link breakage on all architectures which implement their own show_mem James Bottomley
2011-03-24 22:21 ` David Rientjes
2011-03-25 14:13 ` James Bottomley [this message]
2011-03-25 20:02 ` David Rientjes
2011-03-25 18:38 ` Josh Boyer
2011-03-25 10:55 ` Benjamin Herrenschmidt
2011-03-25 14:11 ` James Bottomley
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=1301062421.4073.3.camel@mulgrave.site \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-arch@vger.kernel.org \
--cc=rientjes@google.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).