All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Dmitry <dbaryshkov@gmail.com>
Cc: Pavel Machek <pavel@ucw.cz>, Paul Walmsley <paul@pwsan.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 21:44:50 +0100	[thread overview]
Message-ID: <20080425204450.GC28893@flint.arm.linux.org.uk> (raw)
In-Reply-To: <bc64b4640804251334j7e2fbf30u358e010bc3e5d5ec@mail.gmail.com>

On Sat, Apr 26, 2008 at 12:34:55AM +0400, Dmitry wrote:
> Hi,
> 
> 2008/4/26, Russell King <rmk+lkml@arm.linux.org.uk>:
> > On Fri, Apr 25, 2008 at 12:39:42PM +0200, Pavel Machek wrote:
> >  > 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?
> 
> Why? We do already have the API. And it's pretty normative. And the
> goal of my framework is to allow me and few other people not to
> reinvent the API for non-platform clocks.
> 
> >  That's what will happen if you try to force a framework on folk which
> >  they don't agree with.
> 
> If you don't want to use it, you are free to do so. E.g. you can use
> your own set of functions to implement GPIO api.

Now go back and read what Pavel wrote (which I responsed to - the
implication that your clock API _will_ _be_ forced upon _everyone_) and
you'll see that he has a completely different perspective to what you've
just said.  So rather than replying to my response, why not respond to
Pavel with your points you've made above?

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:

  reply	other threads:[~2008-04-25 20:45 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 [this message]
2008-04-25 20:51           ` Pavel Machek
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=20080425204450.GC28893@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --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=pavel@ucw.cz \
    --cc=philipp.zabel@gmail.com \
    --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 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.