From: Brian Gerst <bgerst@didntduck.org>
To: Andi Kleen <ak@suse.de>
Cc: Andrew Morton <akpm@osdl.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86-64: Use cpumask bitops for cpu_vm_mask
Date: Tue, 07 Mar 2006 09:19:46 -0500 [thread overview]
Message-ID: <440D9682.7070601@didntduck.org> (raw)
In-Reply-To: <200603070718.24748.ak@suse.de>
Andi Kleen wrote:
> On Tuesday 07 March 2006 14:37, Brian Gerst wrote:
>
>>cpu_vm_mask is of type cpumask_t, so use the proper bitops.
>
>
> Doesn't apply.
>
> patching file arch/x86_64/kernel/smp.c
> patching file include/asm-x86_64/mmu_context.h
> Hunk #1 FAILED at 34.
> Hunk #2 FAILED at 50.
> 2 out of 2 hunks FAILED -- rejects in file include/asm-x86_64/mmu_context.h
>
> -Andi
>
>
I diffed against the vanilla kernel. It looks like -mm has the fix to
mmu_context.h already (x86_64-mm-bitops-cleanups.patch), but the patch
to smp.c is still valid.
--
Brian Gerst
prev parent reply other threads:[~2006-03-07 14:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-07 13:37 [PATCH] x86-64: Use cpumask bitops for cpu_vm_mask Brian Gerst
2006-03-07 6:18 ` Andi Kleen
2006-03-07 14:19 ` Brian Gerst [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=440D9682.7070601@didntduck.org \
--to=bgerst@didntduck.org \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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