From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-acpi@vger.kernel.org, Huang Ying <ying.huang@intel.com>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for August 10 (acpi/apei)
Date: Tue, 10 Aug 2010 10:02:28 -0700 [thread overview]
Message-ID: <20100810100228.525d952e.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20100810135601.4777e310.sfr@canb.auug.org.au>
On Tue, 10 Aug 2010 13:56:01 +1000 Stephen Rothwell wrote:
> Hi all,
>
> As the merge window is open, please do not add 2.6.37 material to your
> linux-next included trees until after 2.6.36-rc1.
>
> Changes since 20100809:
on 32-bit i386:
drivers/acpi/apei/erst-dbg.c:106: warning: format '%lx' expects type 'long unsigned int', but argument 3 has type 'ssize_t'
erst-dbg.c:(.text+0xede6d): undefined reference to `__get_user_X'
For the __get_user_X() call, in erst-dbg.c::erst_dbg_ioctl():
case APEI_ERST_CLEAR_RECORD:
rc = get_user(record_id, (u64 __user *)arg);
-> arch/x86/include/asm/uaccess.h:
#ifdef CONFIG_X86_32
#define __get_user_8(__ret_gu, __val_gu, ptr) \
__get_user_x(X, __ret_gu, __val_gu, ptr)
#else
#define __get_user_8(__ret_gu, __val_gu, ptr) \
__get_user_x(8, __ret_gu, __val_gu, ptr)
#endif
so is __get_user_8() not supported on X86_32?
or is this something else?
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-08-10 17:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 3:56 linux-next: Tree for August 10 Stephen Rothwell
2010-08-10 9:56 ` Alan Cox
2010-08-10 16:40 ` [PATCH -next] mfd: tps6586x depends on GPIOLIB Randy Dunlap
2010-08-10 23:14 ` Samuel Ortiz
2010-08-10 17:02 ` Randy Dunlap [this message]
2010-08-11 1:32 ` linux-next: Tree for August 10 (acpi/apei) Huang Ying
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=20100810100228.525d952e.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=ying.huang@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 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).