From: Linus Walleij <linus.walleij@linaro.org>
To: Dave Jones <davej@redhat.com>, Arnd Bergmann <arnd@arndb.de>,
Linus Walleij <linus.walleij@stericsson.com>,
Samuel Ortiz <sameo@linux.intel.com>,
linux-kernel@vger.kernel.org, Lee Jones <lee.jones@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH 10/10] mach-ux500: update and move cpufreq driver
Date: Mon, 16 May 2011 11:02:14 +0200 [thread overview]
Message-ID: <BANLkTimh2Xaz73v-2c0GmcS9wD4+JFWzrw@mail.gmail.com> (raw)
In-Reply-To: <20110510055926.GA2747@redhat.com>
2011/5/10 Dave Jones <davej@redhat.com>:
> Haven't had chance to really read much patches the last few days
> (travelling until the 16th). Due to the patch collisions we'll keep
> seeing on kconfig/Makefiles, should these go via the cpufreq tree,
> or do people want to still push them through their respective arch trees ?
I pushed a patch series yesterday that basically deactivates the
cpufreq driver in the mach-ux500, moves it over to drivers/cpufreq,
updates it, then reactivates it in the new place with a patch to
the Makefile.
Of these changes only the last patch will collide with your tree,
so I pushed all of them except that one to linux-next.
The last patch I plan to submit to Torvalds directly after both
trees have gone into the merge window.
Can you please look into this and ACK the patches if they
seem OK?
Linus Walleij
next prev parent reply other threads:[~2011-05-16 9:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 13:06 [PATCH 10/10] mach-ux500: update and move cpufreq driver Linus Walleij
2011-05-06 13:22 ` Arnd Bergmann
2011-05-10 5:59 ` Dave Jones
2011-05-10 23:54 ` Linus Walleij
2011-05-16 9:02 ` Linus Walleij [this message]
2011-05-17 21:12 ` Dave Jones
2011-05-17 23:07 ` Nicolas Pitre
2011-05-18 5:21 ` Linus Walleij
2011-05-18 5:18 ` Linus Walleij
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=BANLkTimh2Xaz73v-2c0GmcS9wD4+JFWzrw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=arnd@arndb.de \
--cc=davej@redhat.com \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.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;
as well as URLs for NNTP newsgroup(s).