All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org, davej@redhat.com,
	paulus@samba.org, cpufreq@vger.kernel.org,
	benh@kernel.crashing.org
Subject: Re: [PATCH] Add cpufreq driver for Momentum Maple boards
Date: Fri, 17 Jun 2011 13:52:37 +0200	[thread overview]
Message-ID: <201106171352.38707.arnd@arndb.de> (raw)
In-Reply-To: <BANLkTimo6k=Zz+QnP0VaWYf3jDjpFXNL4w@mail.gmail.com>

On Friday 17 June 2011 13:12:56 Dmitry Eremin-Solenikov wrote:
> > I think new cpufreq drivers should live in drivers/cpufreq, not in arch/.
> > We've
> > started moving other drivers away from arch/x86 and arch/arm already.
> 
> What about drivers/cpufreq/powerpc, or it's an unnecessary?

drivers/cpufreq is fine by itself, unless Dave has some preference.

> Should I resumbit it, or there will be massive arch/powerpc ->
> drivers/cpufreq move?

My recommendation would be to submit the new driver for drivers/cpufreq
directly and let Ben take care of the others at a convenient time.

	Arnd

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: "Dmitry Eremin-Solenikov" <dbaryshkov@gmail.com>
Cc: davej@redhat.com, linuxppc-dev@lists.ozlabs.org,
	cpufreq@vger.kernel.org, paulus@samba.org
Subject: Re: [PATCH] Add cpufreq driver for Momentum Maple boards
Date: Fri, 17 Jun 2011 13:52:37 +0200	[thread overview]
Message-ID: <201106171352.38707.arnd@arndb.de> (raw)
In-Reply-To: <BANLkTimo6k=Zz+QnP0VaWYf3jDjpFXNL4w@mail.gmail.com>

On Friday 17 June 2011 13:12:56 Dmitry Eremin-Solenikov wrote:
> > I think new cpufreq drivers should live in drivers/cpufreq, not in arch/.
> > We've
> > started moving other drivers away from arch/x86 and arch/arm already.
> 
> What about drivers/cpufreq/powerpc, or it's an unnecessary?

drivers/cpufreq is fine by itself, unless Dave has some preference.

> Should I resumbit it, or there will be massive arch/powerpc ->
> drivers/cpufreq move?

My recommendation would be to submit the new driver for drivers/cpufreq
directly and let Ben take care of the others at a convenient time.

	Arnd

  reply	other threads:[~2011-06-17 11:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-21 10:28 [PATCH] Add cpufreq driver for Momentum Maple boards Dmitry Eremin-Solenikov
2011-05-21 10:28 ` Dmitry Eremin-Solenikov
2011-05-30 11:57 ` Dmitry Eremin-Solenikov
2011-05-30 11:57   ` Dmitry Eremin-Solenikov
2011-06-04  9:00   ` Dmitry Eremin-Solenikov
2011-06-04  9:00     ` Dmitry Eremin-Solenikov
2011-06-04 10:29     ` Benjamin Herrenschmidt
2011-06-04 10:29       ` Benjamin Herrenschmidt
2011-06-04 10:39       ` Dmitry Eremin-Solenikov
2011-06-04 10:39         ` Dmitry Eremin-Solenikov
2011-06-17  4:14 ` Benjamin Herrenschmidt
2011-06-17  4:14   ` Benjamin Herrenschmidt
2011-06-17  8:49   ` Dmitry Eremin-Solenikov
2011-06-17  8:49     ` Dmitry Eremin-Solenikov
2011-06-17  9:17     ` Arnd Bergmann
2011-06-17 11:12       ` Dmitry Eremin-Solenikov
2011-06-17 11:12         ` Dmitry Eremin-Solenikov
2011-06-17 11:52         ` Arnd Bergmann [this message]
2011-06-17 11:52           ` Arnd Bergmann
2011-06-17 20:07         ` Dave Jones
2011-06-17 20:07           ` Dave Jones

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=201106171352.38707.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=benh@kernel.crashing.org \
    --cc=cpufreq@vger.kernel.org \
    --cc=davej@redhat.com \
    --cc=dbaryshkov@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paulus@samba.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.