From: Richard Weinberger <richard@nod.at>
To: Sergei Trofimovich <slyich@gmail.com>
Cc: Jeff Dike <jdike@addtoit.com>,
user-mode-linux-devel@lists.sourceforge.net,
user-mode-linux-user@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [RFC] um: x86: unbreak build by reintroducing this_cpu_cmpxchg16b_emu
Date: Wed, 6 Apr 2011 23:31:33 +0200 [thread overview]
Message-ID: <201104062331.34205.richard@nod.at> (raw)
In-Reply-To: <20110407001837.12e6f01c@sf.home>
Sergei,
Am Mittwoch 06 April 2011, 23:18:37 schrieb Sergei Trofimovich:
> I'm sure fix can be nices, but initial patch should express an idea.
Please send patches not as attachment.
I think this patch is only needed on x86_64.
Um builds fine on my main machine (i386).
It seems to fail on x86_64 when using CONFIG_SLUB=y.
> The main offender is privileged 'cli'.
>
> Thanks!
Thanks,
//richard
prev parent reply other threads:[~2011-04-06 21:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 21:18 [PATCH] [RFC] um: x86: unbreak build by reintroducing this_cpu_cmpxchg16b_emu Sergei Trofimovich
2011-04-06 21:31 ` Richard Weinberger [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=201104062331.34205.richard@nod.at \
--to=richard@nod.at \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=slyich@gmail.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@lists.sourceforge.net \
/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