public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Peter Stuge <peter@stuge.se>
Cc: Greg KH <greg@kroah.com>,
	Jimmy RUBIN <jimmy.rubin@stericsson.com>,
	Dan JOHANSSON <dan.johansson@stericsson.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Linus Walleij <linus.walleij@linaro.org>,
	Marcus LORENTZON <marcus.xm.lorentzon@stericsson.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	dri-devel@lists.freedesktop.org,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: [PATCH 09/10] MCDE: Add build files and bus
Date: Wed, 1 Dec 2010 13:02:48 +0000	[thread overview]
Message-ID: <20101201130248.GA21710@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20101201125339.30270.qmail@stuge.se>

On Wed, Dec 01, 2010 at 01:53:39PM +0100, Peter Stuge wrote:
> Russell King - ARM Linux wrote:
> > I feel it would be better to allow the current situation to continue.
> 
> I think this misses the point, and is somewhat redundant; I think
> everyone knows that it is easiest to never change anything. But
> then nothing improves.
> 
> 
> > If we start telling people that they can't use statically declared
> > devices without first having an alternative,
> 
> I would consider it early warning that the way things have been done
> before will go away. And I would thus write drivers in a way that
> demonstrates and includes that understanding.

Clearly you haven't understood my point.

If we go down the route you suggest, we're going to end up with
everyone doing something different, which will then need to be cleaned
up once the proper solution is in place.  That could easily become
much more work than just waiting for the proper solution.

What is easier - to fix all instances which statically declare, or
to fix all instances which statically declare _and_ all the bodged up
alternative solutions?

  reply	other threads:[~2010-12-01 13:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <F45880696056844FA6A73F415B568C6953604E802E@EXDCVYMBSTM006.EQ1STM.local>
     [not found] ` <201011251747.48365.arnd@arndb.de>
     [not found]   ` <C832F8F5D375BD43BFA11E82E0FE9FE0082586F430@EXDCVYMBSTM005.EQ1STM.local>
2010-11-26 11:24     ` [PATCH 09/10] MCDE: Add build files and bus Arnd Bergmann
2010-11-30 14:18       ` Linus Walleij
2010-11-30 15:21         ` Arnd Bergmann
2010-11-30 16:24           ` Greg KH
2010-11-30 18:40           ` Russell King - ARM Linux
2010-11-30 18:48             ` Greg KH
2010-11-30 22:05               ` Russell King - ARM Linux
2010-11-30 23:05                 ` Greg KH
2010-11-30 23:42                   ` Russell King - ARM Linux
2010-11-30 23:49                     ` Greg KH
2010-12-01 12:53                     ` Peter Stuge
2010-12-01 13:02                       ` Russell King - ARM Linux [this message]
2010-12-01 15:39                     ` Arnd Bergmann
2010-12-04  6:52       ` Dave Airlie
2010-12-04 21:34       ` Alex Deucher
2010-12-05 11:28         ` Daniel Vetter
2011-03-12 15:59           ` Rob Clark
2011-03-14 14:03             ` Marcus Lorentzon
2011-03-14 20:35               ` Rob Clark
2010-12-16 18:26       ` Marcus Lorentzon
2010-12-17 11:22         ` Arnd Bergmann
2010-12-17 12:02           ` Marcus Lorentzon

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=20101201130248.GA21710@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=arnd@arndb.de \
    --cc=dan.johansson@stericsson.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=greg@kroah.com \
    --cc=jimmy.rubin@stericsson.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=marcus.xm.lorentzon@stericsson.com \
    --cc=peter@stuge.se \
    /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