From: Liu Gang <Gang.Liu@freescale.com>
To: Paul Gortmaker <paul.gortmaker@gmail.com>
Cc: Alexandre.Bounine@idt.com, linux-next@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH/RFC] rapidio: temporarily exclude FSL_RIO from 64 bit builds
Date: Mon, 27 Feb 2012 14:48:48 +0800 [thread overview]
Message-ID: <1330325328.23420.93.camel@10.ap.freescale.net> (raw)
In-Reply-To: <CAP=VYLroaEKncpy7VBobJdXijnDS5UdTV7qPG2A--SicnGvFSg@mail.gmail.com>
On Sun, 2012-02-26 at 20:26 -0500, Paul Gortmaker wrote:
> Hi Ben,
>
> Given a week has passed with the absence of any feedback
> with respect to SRIO on 64 bit, are you OK with applying the
> below patch[1] pretty much as-is?
Hi, Paul, Ben,
Sorry for the late reply because of my other urgent issues. I also found
these errors of 64bit building last week. I'll provide patch for this
issue as soon as possible.
Thanks.
Best Regards,
Liu Gang
prev parent reply other threads:[~2012-02-27 6:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 23:10 [PATCH/RFC] rapidio: temporarily exclude FSL_RIO from 64 bit builds Paul Gortmaker
2012-02-27 1:26 ` Paul Gortmaker
2012-02-27 1:49 ` Benjamin Herrenschmidt
2012-02-27 6:48 ` Liu Gang [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=1330325328.23420.93.camel@10.ap.freescale.net \
--to=gang.liu@freescale.com \
--cc=Alexandre.Bounine@idt.com \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paul.gortmaker@gmail.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).