From: Martyn Welch <martyn.welch@ge.com>
To: Namhyung Kim <namhyung@gmail.com>
Cc: Greg KH <greg@kroah.com>, Greg Kroah-Hartman <gregkh@suse.de>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/8] Staging: vme_bridge: mark vme_master_resource->kern_base as __iomem
Date: Tue, 14 Dec 2010 09:15:45 +0000 [thread overview]
Message-ID: <4D0735C1.5090100@ge.com> (raw)
In-Reply-To: <1292302327.1696.31.camel@leonhard>
On 14/12/10 04:52, Namhyung Kim wrote:
> 2010-12-13 (월), 10:36 -0800, Greg KH:
>> On Mon, Dec 13, 2010 at 10:16:30PM +0900, Namhyung Kim wrote:
>>> vme_master_resource->kern_base is mapped by ioremap_nocache()
>>> thus should be marked as __iomem.
>>>
>>> Signed-off-by: Namhyung Kim <namhyung@gmail.com>
>>
>> I need some acks from Martyn on this series (minus the broken 1/8 patch)
>> before I can apply them. Martyn?
>>
>> thanks,
>>
>> greg k-h
>
> Now I've checked -next tree and found patch 2 (partially), 3, 5, 6 and 8
> are already in the tree. Sorry for my carelessness :( Will send v2.
>
>
I had a quick peek at these patches when they can in yesterday, I
thought there may have been quite a bit of overlap with the patches that
Emilio posted and needed to find time to look in more detail.
Martyn
--
Martyn Welch (Principal Software Engineer) | Registered in England and
GE Intelligent Platforms | Wales (3828642) at 100
T +44(0)127322748 | Barbirolli Square,
Manchester,
E martyn.welch@ge.com | M2 3AB VAT:GB 927559189
next prev parent reply other threads:[~2010-12-14 9:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 13:16 [PATCH 1/8] Staging: vme_ca91cx42: fix compiler warning on 64-bit build Namhyung Kim
2010-12-13 13:16 ` [PATCH 2/8] Staging: vme_bridge: mark vme_master_resource->kern_base as __iomem Namhyung Kim
2010-12-13 18:36 ` Greg KH
2010-12-14 4:52 ` Namhyung Kim
2010-12-14 9:15 ` Martyn Welch [this message]
2010-12-13 13:16 ` [PATCH 3/8] Staging: vme_ca91cx42: mark ca91cx42_driver->base " Namhyung Kim
2010-12-13 13:16 ` [PATCH 4/8] Staging: vme_ca91cx42: remove unreachable code Namhyung Kim
2010-12-13 13:16 ` [PATCH 5/8] Staging: vme_ca91cx42: make functions static Namhyung Kim
2010-12-13 13:16 ` [PATCH 6/8] Staging: vme_tsi148: mark tsi148_driver->base as __iomem Namhyung Kim
2010-12-13 13:16 ` [PATCH 7/8] Staging: vme_tsi148: remove unreachable code Namhyung Kim
2010-12-13 13:16 ` [PATCH 8/8] Staging: vme_tsi148: make functions static Namhyung Kim
2010-12-13 13:50 ` [PATCH 1/8] Staging: vme_ca91cx42: fix compiler warning on 64-bit build Jiri Slaby
2010-12-13 14:16 ` Namhyung Kim
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=4D0735C1.5090100@ge.com \
--to=martyn.welch@ge.com \
--cc=devel@driverdev.osuosl.org \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.