From: amwang@redhat.com (Cong Wang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] highmem: Fix ARM build break due to __kmap_atomic rename
Date: Wed, 07 Dec 2011 17:26:56 +0800 [thread overview]
Message-ID: <4EDF3160.7070800@redhat.com> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF1750B774A6@HQMAIL01.nvidia.com>
? 2011?12?07? 03:52, Stephen Warren ??:
> Nicolas Pitre wrote at Tuesday, December 06, 2011 12:42 PM:
>> On Tue, 6 Dec 2011, Stephen Warren wrote:
>>> Git commit 37bfbb9 "highmem: kill all __kmap_atomic()" renamed
>>> __kmap_atomic to kmap_atomic. However, arch/arm/include/asm/highmem.h
>>> wasn't updated for that change. This change does so, and fixes the
>>> ARM build break.
>>>
>>> Signed-off-by: Stephen Warren<swarren@nvidia.com>
>>> ---
>>> This shows up in next-20111206 at least.
>>
>> Commit 37bfbb9 doesn't show up in anything which is stable yet. Would
>> be best to ask the original author to fix his branch.
>
> Yes, I assumed that Cong would squash this into his/her tree that's in
> linux-next.
>
Thanks for your patch, Stephen!
I have squashed your patch into that commit,
commit 5bf31c9a5de45a6ea6628fe84c043ac38babf393
Author: Cong Wang <amwang@redhat.com>
Date: Sat Nov 26 10:53:39 2011 +0800
highmem: kill all __kmap_atomic()
[swarren at nvidia.com: highmem: Fix ARM build break due to __kmap_atomic rename]
Signed-off-by: Stephen Warren <swarren@nvidia.com>
Signed-off-by: Cong Wang <amwang@redhat.com>
prev parent reply other threads:[~2011-12-07 9:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 18:50 [PATCH] highmem: Fix ARM build break due to __kmap_atomic rename Stephen Warren
2011-12-06 19:41 ` Nicolas Pitre
2011-12-06 19:52 ` Stephen Warren
2011-12-07 9:26 ` Cong Wang [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=4EDF3160.7070800@redhat.com \
--to=amwang@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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).