All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Tomoya MORINAGA <tomoya-linux@dsn.okisemi.com>
Cc: Greg KH <greg@kroah.com>, Alan Cox <alan@linux.intel.com>,
	linux-kernel@vger.kernel.org, Ben Dooks <ben-linux@fluff.org>,
	Kukjin Kim <kgene.kim@samsung.com>,
	Mike Frysinger <vapier@gentoo.org>,
	Feng Tang <feng.tang@intel.com>,
	Tobias Klauser <tklauser@distanz.ch>,
	yong.y.wang@intel.com, qi.wang@intel.com, kok.howg.ewe@intel.com,
	andrew.chih.howe.khor@intel.com
Subject: Re: Serial: EG20T: add PCH_UART driver
Date: Mon, 6 Dec 2010 16:15:10 -0800	[thread overview]
Message-ID: <20101207001510.GA28176@suse.de> (raw)
In-Reply-To: <F707E6EFF9AF4169B5E0C55B5AB2757B@hacdom.okisemi.com>

On Tue, Dec 07, 2010 at 09:05:34AM +0900, Tomoya MORINAGA wrote:
> On Wednesday, December 01, 2010 10:24 AM, Greg KH wrote:
> >I've applied this, but I now get the following warnings when building
> >the code:
> 
> Sorry, for late.
> I can't see these warnings.
> I think we build with 32bit Linux PC.
> But we don't have 64-bit PC.
> 
> I tried build with "-m64" option on our PC, I can see the following error.
> : sorry, unimplemented: 64-bit mode not compiled in
> 
> Can I see the warnings using our PC ?
> If you have any information, let me know how to do.

Yes, use a version of gcc that will build in 64bit mode :)

Or use a modern processor (I find it hard to believe you don't have
access to a 64bit intel processor these days...)

thanks,

greg k-h

      reply	other threads:[~2010-12-07  0:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-17  0:55 [PATCH v5] EG20T: Update PCH_UART driver to 2.6.36 Tomoya MORINAGA
2010-11-17 11:33 ` Alan Cox
2010-12-01  1:24 ` Serial: EG20T: add PCH_UART driver Greg KH
2010-12-01  2:33   ` Tomoya MORINAGA
2010-12-07  0:05   ` Tomoya MORINAGA
2010-12-07  0:15     ` Greg KH [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=20101207001510.GA28176@suse.de \
    --to=gregkh@suse.de \
    --cc=alan@linux.intel.com \
    --cc=andrew.chih.howe.khor@intel.com \
    --cc=ben-linux@fluff.org \
    --cc=feng.tang@intel.com \
    --cc=greg@kroah.com \
    --cc=kgene.kim@samsung.com \
    --cc=kok.howg.ewe@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=qi.wang@intel.com \
    --cc=tklauser@distanz.ch \
    --cc=tomoya-linux@dsn.okisemi.com \
    --cc=vapier@gentoo.org \
    --cc=yong.y.wang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.