All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: "devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	"ss@aao.gov.au" <ss@aao.gov.au>, Greg KH <gregkh@suse.de>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Staging: dt3155: Cleanup memory mapped i/o access
Date: Thu, 6 May 2010 13:25:35 -0700	[thread overview]
Message-ID: <20100506202535.GA28600@kroah.com> (raw)
In-Reply-To: <0D753D10438DA54287A00B0270842697636ECB4D7B@AUSP01VMBX24.collaborationhost.net>

On Thu, May 06, 2010 at 11:59:03AM -0500, H Hartley Sweeten wrote:
> On Tuesday, May 04, 2010 2:23 PM, 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.
> >
> > While here, make dt3155_lbase static since it is only used in the
> > dt3155_drv.c file.  Also, remove the global variable dt3155_bbase
> > since it is not used anywhere in the code.
> >
> > Where is makes sense, create a local 'mmio' variable instead of using
> > dt3155_lbase[minor] to make the code more readable.
> >
> > This change also affects the {Read|Write}I2C functions so they are
> > also modified as needed.
> >
> > Signed-off-by: H Hartley Sweeten <hsweeten@visionengravers.com>
> > Cc: Greg Kroah-Hartman <gregkh@suse.de>
> > Cc: Scott Smedley <ss@aao.gov.au>
> >
> 
> Greg,
> 
> Did this patch fair any better when trying to merge it?

No, not at all :(

> If there is still an issue I will wait until Linus' tree, linux-next,
> and your staging-next branch appear to be more in sync.

Yes, please wait a bit, I really don't know what is going on here,
sorry.

greg k-h

  reply	other threads:[~2010-05-06 20:27 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-28 17:23 [PATCH] Staging: dt3155: Cleanup memory mapped i/o access H Hartley Sweeten
2010-04-30 21:56 ` Greg KH
2010-05-02 17:35   ` H Hartley Sweeten
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 [this message]
2010-06-21 15:51                                     ` [PATCH v2] " H Hartley Sweeten
2010-06-22 22:39                                       ` Greg KH
2010-06-22 22:45                                         ` H Hartley Sweeten
2010-06-22 23:04                                           ` Greg KH
2010-06-22 23:36                                             ` H Hartley Sweeten
2010-05-04  0:49                 ` H Hartley Sweeten
  -- strict thread matches above, loose matches on Subject: below --
2010-06-22 23:38 [PATCH v2] " H Hartley Sweeten
2010-06-23 22:23 ` Greg KH

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=20100506202535.GA28600@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 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.