From: Greg KH <greg@kroah.com>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: ss@aao.gov.au, gregkh@suse.de, devel@driverdev.osuosl.org,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Staging: dt3155: Cleanup memory mapped i/o access
Date: Wed, 23 Jun 2010 15:23:20 -0700 [thread overview]
Message-ID: <20100623222317.GA14659@kroah.com> (raw)
In-Reply-To: <201006221638.50754.hartleys@visionengravers.com>
On Tue, Jun 22, 2010 at 04:38:50PM -0700, H Hartley Sweeten wrote:
> The macros ReadMReg and WriteMReg are really just private versions of
> the kernel's readl and writel functions. Use the kernel's functions
> instead. And since ioremap returns a (void __iomem *) not a (u8 *),
> change all the uses of dt3155_lbase to reflect this.
<snip>
Whatever you did to fix the email client issue up, it worked, thanks.
greg k-h
next prev parent reply other threads:[~2010-06-23 22:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 23:38 [PATCH v2] Staging: dt3155: Cleanup memory mapped i/o access H Hartley Sweeten
2010-06-23 22:23 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-04-28 17:23 [PATCH] " H Hartley Sweeten
2010-04-30 21:56 ` Greg KH
2010-05-02 18:00 ` H Hartley Sweeten
2010-05-03 18:59 ` Greg KH
2010-05-03 20:15 ` H Hartley Sweeten
2010-05-03 21:17 ` Greg KH
2010-05-03 22:24 ` H Hartley Sweeten
2010-05-03 22:45 ` H Hartley Sweeten
2010-05-03 23:33 ` H Hartley Sweeten
2010-05-03 23:40 ` Greg KH
2010-05-03 23:41 ` Greg KH
2010-05-03 23:59 ` Joe Perches
2010-05-04 2:54 ` Greg KH
2010-05-04 19:07 ` Joe Perches
2010-05-04 20:02 ` H Hartley Sweeten
2010-05-04 20:12 ` Greg KH
2010-05-04 20:53 ` H Hartley Sweeten
2010-05-04 21:02 ` Greg KH
2010-05-04 21:22 ` H Hartley Sweeten
2010-05-06 16:59 ` H Hartley Sweeten
2010-05-06 20:25 ` Greg KH
2010-05-04 0:49 ` H Hartley Sweeten
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=20100623222317.GA14659@kroah.com \
--to=greg@kroah.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=hartleys@visionengravers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ss@aao.gov.au \
/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