From: Valdis.Kletnieks@vt.edu (Valdis.Kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: kernel build error
Date: Wed, 20 Mar 2013 13:32:15 -0400 [thread overview]
Message-ID: <2841.1363800735@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Wed, 20 Mar 2013 00:07:57 -0700." <20130320070757.GC6275@gmail.com>
On Wed, 20 Mar 2013 00:07:57 -0700, Kumar amit mehta said:
> I forgot that 'uname -m' will return me the kernel version and _not_ the CPU
> architecture. The CPU on my machine seem to be 64 bit (/proc/cpuinfo|grep flags
> shows 'lm'). So my understanding is that I've a 32 bit kernel running on a 64
> bit machine.
Or more correctly, you have a kernel actually running in 32-bit mode on
a machine that is 64-bit capable.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 865 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20130320/7abe72e5/attachment.bin
next prev parent reply other threads:[~2013-03-20 17:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-17 15:28 kernel build error Kumar amit mehta
2013-03-18 4:21 ` Mulyadi Santosa
2013-03-19 5:28 ` Kumar amit mehta
2013-03-19 14:43 ` Mulyadi Santosa
2013-03-20 6:56 ` Kumar amit mehta
2013-03-20 7:07 ` Kumar amit mehta
2013-03-20 9:48 ` Ben Wu
2013-03-20 9:49 ` wake_lock in linux kernel Ben Wu
2013-03-21 4:34 ` Yuva Raj
2013-03-20 17:32 ` Valdis.Kletnieks at vt.edu [this message]
2013-03-21 6:16 ` kernel build error Kumar amit mehta
2013-03-22 3:41 ` Mulyadi Santosa
2013-03-22 10:17 ` Kumar amit mehta
2013-03-24 5:49 ` Mulyadi Santosa
2013-03-25 5:04 ` Kumar amit mehta
2013-03-25 7:36 ` Mulyadi Santosa
[not found] ` <20130331044544.GA3291@gmail.com>
2013-04-02 3:04 ` Mulyadi Santosa
2013-04-02 6:19 ` Kumar amit mehta
2013-04-02 13:40 ` Mulyadi Santosa
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=2841.1363800735@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@lists.kernelnewbies.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).