From: benh@kernel.crashing.org (Benjamin Herrenschmidt)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC,PATCH 1/7] arm: add a common struct clk
Date: Sat, 09 Jan 2010 06:33:12 +1100 [thread overview]
Message-ID: <1262979192.585.42.camel@pasglop> (raw)
In-Reply-To: <BD79186B4FD85F4B8E60E381CAEE1909020896AE@mi8nycmail19.Mi8.com>
On Fri, 2010-01-08 at 11:25 -0500, H Hartley Sweeten wrote:
>
> I was just trying to figure out if it was worth trying to use this in
> mach-ep93xx. It looks like it would be pretty straight forward but
> the implementation is going to use quite a bit more memory because to the
> size of the common struct.
>
> For now I think I will leave ep93xx as it is.
How much memory do you have on that platform ? How much more memory is
going to be used by the implementation ?
It may not be the case in this particular instance but I find it funny
when people complain about something that will use a few hundred more
bytes, maybe one or two k more, on machines that have hundreds of MB of
RAM at the expense of code flexibility, reusability and
maintainability :-)
Cheers,
Ben.
next prev parent reply other threads:[~2010-01-08 19:33 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 23:44 [RFC,PATCH 1/7] arm: add a common struct clk Jeremy Kerr
2010-01-07 23:44 ` [RFC,PATCH 7/7] arm/icst307: remove icst307_ps_to_vco Jeremy Kerr
2010-01-07 23:44 ` [RFC,PATCH 2/7] arm: generic support for fixed-rate clocks Jeremy Kerr
2010-01-07 23:44 ` [RFC, PATCH 6/7] arm/icst307: use common struct clk, unify realview and versatile clocks Jeremy Kerr
2010-01-08 1:11 ` H Hartley Sweeten
2010-01-08 1:35 ` Jeremy Kerr
2010-01-07 23:44 ` [RFC,PATCH 5/7] arm/realview: use generic struct clk Jeremy Kerr
2010-01-07 23:44 ` [RFC,PATCH 3/7] arm/versatile: " Jeremy Kerr
2010-01-07 23:44 ` [RFC,PATCH 4/7] arm/versatile: remove oscoff from clk_versatile Jeremy Kerr
2010-01-08 0:30 ` [RFC,PATCH 1/7] arm: add a common struct clk H Hartley Sweeten
2010-01-08 1:20 ` Jeremy Kerr
2010-01-08 3:26 ` Jeremy Kerr
2010-01-08 9:42 ` Russell King - ARM Linux
2010-01-08 10:01 ` Benjamin Herrenschmidt
2010-01-08 11:18 ` Russell King - ARM Linux
2010-01-08 11:45 ` Benjamin Herrenschmidt
2010-01-08 12:59 ` Russell King - ARM Linux
2010-01-08 19:45 ` Benjamin Herrenschmidt
2010-01-11 3:37 ` Jeremy Kerr
2010-01-12 8:00 ` Francesco VIRLINZI
2010-01-12 8:50 ` Benjamin Herrenschmidt
2010-01-08 16:25 ` H Hartley Sweeten
2010-01-08 19:33 ` Benjamin Herrenschmidt [this message]
2010-01-08 1:17 ` Benjamin Herrenschmidt
2010-01-08 1:38 ` Jeremy Kerr
2010-01-11 5:38 ` Jeremy Kerr
2010-01-11 10:46 ` Mark Brown
2010-01-11 19:48 ` Benjamin Herrenschmidt
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=1262979192.585.42.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linux-arm-kernel@lists.infradead.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 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.