From: Pavel Machek <pavel@ucw.cz>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Paul Walmsley <paul@pwsan.com>, Dmitry <dbaryshkov@gmail.com>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
Haavard Skinnemoen <haavard.skinnemoen@atmel.com>,
Paul Mundt <lethal@linux-sh.org>,
pHilipp Zabel <philipp.zabel@gmail.com>,
tony@atomide.com, David Brownell <david-b@pacbell.net>,
hiroshi.DOYU@nokia.com
Subject: Re: [PATCH 0/5] Clocklib: generic clocks framework
Date: Fri, 25 Apr 2008 22:51:51 +0200 [thread overview]
Message-ID: <20080425205151.GA6251@elf.ucw.cz> (raw)
In-Reply-To: <20080425202010.GA28893@flint.arm.linux.org.uk>
Hi!
> > WTF? There are currently around 10 copies of clock code in the tree,
> > every one slightly different. If this can help us get rid of all that
> > crap, that's a GOOD THING, normative or not.
>
> At the expense of people going off and inventing their own APIs because
> they find that the "normatived" clock API doesn't do what they need to?
Just now, everyone just cuts&copies clock.c. I do not think "new"
situation can worse than that.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-04-25 20:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-20 8:29 [PATCH 0/5] Clocklib: generic clocks framework Dmitry Baryshkov
2008-04-20 8:30 ` [PATCH 1/5] Clocklib: add generic framework for managing clocks Dmitry Baryshkov
2008-04-20 8:30 ` [PATCH 2/5] Clocklib: debugfs support Dmitry Baryshkov
2008-04-20 8:31 ` [PATCH 3/5] Clocklib: support sa1100 sub-arch Dmitry Baryshkov
2008-04-20 8:31 ` [PATCH 4/5] Clocklib: support ARM pxa sub-arch Dmitry Baryshkov
2008-04-20 8:31 ` [PATCH 5/5] Clocklib: Use correct clock for IrDA on pxa Dmitry Baryshkov
2008-04-21 7:44 ` [PATCH 0/5] Clocklib: generic clocks framework Paul Walmsley
2008-04-21 8:48 ` Dmitry
2008-04-21 9:15 ` Hiroshi DOYU
2008-04-25 9:36 ` Paul Walmsley
2008-04-25 10:39 ` Pavel Machek
2008-04-25 20:20 ` Russell King
2008-04-25 20:34 ` Dmitry
2008-04-25 20:44 ` Russell King
2008-04-25 20:51 ` Pavel Machek [this message]
2008-04-25 21:13 ` Russell King
2008-04-25 21:36 ` Dmitry
2008-04-26 8:47 ` Dmitry
2008-04-26 18:02 ` David Brownell
2008-05-02 5:23 ` Paul Walmsley
2008-05-02 9:40 ` Dmitry
2008-05-05 7:59 ` Pavel Machek
2008-04-25 22:46 ` David Brownell
2008-04-26 8:38 ` Dmitry
2008-04-26 16:29 ` David Brownell
-- strict thread matches above, loose matches on Subject: below --
2008-04-20 8:28 Dmitry Baryshkov
2008-04-13 14:41 Dmitry Baryshkov
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=20080425205151.GA6251@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=david-b@pacbell.net \
--cc=dbaryshkov@gmail.com \
--cc=haavard.skinnemoen@atmel.com \
--cc=hiroshi.DOYU@nokia.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=philipp.zabel@gmail.com \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=tony@atomide.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