From: Greg KH <greg@kroah.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Arnd Bergmann <arnd@arndb.de>,
Linus Walleij <linus.walleij@linaro.org>,
Jimmy RUBIN <jimmy.rubin@stericsson.com>,
Dan JOHANSSON <dan.johansson@stericsson.com>,
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: Tue, 30 Nov 2010 15:49:37 -0800 [thread overview]
Message-ID: <20101130234937.GA7156@kroah.com> (raw)
In-Reply-To: <20101130234215.GE8521@n2100.arm.linux.org.uk>
On Tue, Nov 30, 2010 at 11:42:15PM +0000, Russell King - ARM Linux wrote:
> > It's a work in progress, but wherever possible, I encourage people to
> > not make 'struct device' static.
>
> Right, so saying to ARM developers that they can't submit code which
> adds new static device structures is rather problematical then, and
> effectively brings a section of kernel development to a complete
> standstill - it means no support for additional ARM platforms until
> this issue is resolved. (This "condition" was mentioned by Arnd
> earlier in this thread, and was put in such a way that it was now
> a hard and fast rule.)
Sorry, I didn't mean for that to be mentioned that way at all, as I know
the issues that are keeping this from happening.
> I feel it would be better to allow the current situation to continue.
> If we start telling people that they can't use statically declared
> devices without first having an alternative, we'll end up with people
> inventing their own individual - and different - solutions to this
> problem, which could actually make the problem harder to resolve in
> the longer term.
Ok, but again, I do encourage, wherever possible, that people do not
statically create a 'struct device'.
thanks,
greg k-h
next prev parent reply other threads:[~2010-11-30 23:50 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 [this message]
2010-12-01 12:53 ` Peter Stuge
2010-12-01 13:02 ` Russell King - ARM Linux
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=20101130234937.GA7156@kroah.com \
--to=greg@kroah.com \
--cc=arnd@arndb.de \
--cc=dan.johansson@stericsson.com \
--cc=dri-devel@lists.freedesktop.org \
--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=linux@arm.linux.org.uk \
--cc=marcus.xm.lorentzon@stericsson.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox