public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: David Brownell <david-b@pacbell.net>
Cc: linux-omap-open-source@linux.omap.com,
	linux-omap@vger.kernel.org, Hiroshi.DOYU@nokia.com
Subject: Re: [PATCH 2/3] ARM: OMAP: Change MMU to use sysdev_class?
Date: Mon, 3 Dec 2007 14:56:47 -0800	[thread overview]
Message-ID: <20071203225647.GH4105@atomide.com> (raw)
In-Reply-To: <20071203225043.13E3723C959@adsl-69-226-248-13.dsl.pltn13.pacbell.net>

* David Brownell <david-b@pacbell.net> [071203 14:50]:
> > What do you guys think? Should we change it, or keep using class device?
> 
> "struct class_device" is going to vanish ... but what I saw
> here was "struct class", which won't ...

Yes sorry, "struct class", not "class_device". The "struct
class_device" conversion to "struct device" was done a while back.

The reason why I'm thinking "struct class" may be still the way to go
for general MMU stuff is that eventually some parts could be arch
independent.

Regards,

Tony

  reply	other threads:[~2007-12-03 22:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-03 22:26 [PATCH 1/3] ARM: OMAP: User GPLv2 for MMU, make checkpatch.pl happier Tony Lindgren
2007-12-03 22:40 ` [PATCH 2/3] ARM: OMAP: Change MMU to use sysdev_class? Tony Lindgren
2007-12-03 22:46   ` [PATCH 3/3] ARM: OMAP: Add MMU framework Tony Lindgren
2007-12-03 22:59     ` Paul Mundt
2007-12-03 22:50   ` [PATCH 2/3] ARM: OMAP: Change MMU to use sysdev_class? David Brownell
2007-12-03 22:56     ` Tony Lindgren [this message]
2007-12-03 22:57     ` Paul Mundt
2007-12-03 23:03       ` Tony Lindgren
2007-12-04  6:34 ` [PATCH 1/3] ARM: OMAP: User GPLv2 for MMU, make checkpatch.pl happier Trilok Soni
2007-12-04  8:24   ` Paul Mundt
2007-12-04  8:42     ` Trilok Soni

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=20071203225647.GH4105@atomide.com \
    --to=tony@atomide.com \
    --cc=Hiroshi.DOYU@nokia.com \
    --cc=david-b@pacbell.net \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=linux-omap@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