From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 07/18] cpufreq: s3c24xx: move cpufreq driver to drivers/cpufreq
Date: Fri, 5 Apr 2013 12:36:34 +0530 [thread overview]
Message-ID: <CAKohpokk1Q+0gRpeW=ts0a8D+rGAUpHu62X+7ejdpfom_B6FYA@mail.gmail.com> (raw)
In-Reply-To: <2a5901ce31c9$95160980$bf421c80$%kim@samsung.com>
On 5 April 2013 12:18, Kukjin Kim <kgene.kim@samsung.com> wrote:
> Basically, this moving looks good to me, but should be re-worked based on
> for-next of samsung tree because this touches too many samsung stuff so this
> should be sent to upstream via samsung tree.
Hmm... Its already applied in Rafael's tree. But it doesn't mean that
it can't be
moved to your tree if there is a issue.
What tree/branch? I used:
git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git for-next
> Applying: cpufreq: s3c24xx: move cpufreq driver to drivers/cpufreq
> error: patch failed: arch/arm/Kconfig:2166
> error: arch/arm/Kconfig: patch does not apply
above two are obvious as you haven't applied other patches in this series.
> error: patch failed: arch/arm/mach-s3c24xx/Kconfig:28
> error: arch/arm/mach-s3c24xx/Kconfig: patch does not apply
> error: patch failed: arch/arm/mach-s3c24xx/Makefile:17
> error: arch/arm/mach-s3c24xx/Makefile: patch does not apply
> error: patch failed: drivers/cpufreq/Makefile:63
> error: drivers/cpufreq/Makefile: patch does not apply
Same here.
> error: drivers/cpufreq/s3c2412-cpufreq.c: does not exist in index
I can still see it in for-next.
Attached is my patch based of your for-next
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-cpufreq-s3c24xx-move-cpufreq-driver-to-drivers-cpufr.patch
Type: application/octet-stream
Size: 18050 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130405/2fb30bb6/attachment-0001.obj>
next prev parent reply other threads:[~2013-04-05 7:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1365079581.git.viresh.kumar@linaro.org>
2013-04-04 12:54 ` [PATCH 01/18] cpufreq: ARM: Arrange drivers in alphabetical order Viresh Kumar
2013-04-04 12:54 ` [PATCH 02/18] cpufreq: tegra: Move driver to drivers/cpufreq Viresh Kumar
2013-04-04 12:54 ` [PATCH 03/18] cpufreq: davinci: move cpufreq " Viresh Kumar
2013-04-04 12:54 ` [PATCH 04/18] cpufreq: pxa3xx: " Viresh Kumar
2013-04-04 12:54 ` [PATCH 05/18] cpufreq: pxa2xx: " Viresh Kumar
2013-04-04 12:54 ` [PATCH 06/18] cpufreq: integrator: " Viresh Kumar
2013-04-04 12:54 ` [PATCH 07/18] cpufreq: s3c24xx: " Viresh Kumar
2013-04-05 6:48 ` Kukjin Kim
2013-04-05 7:06 ` Viresh Kumar [this message]
2013-04-05 11:36 ` Rafael J. Wysocki
2013-04-08 9:15 ` Kukjin Kim
2013-04-08 9:18 ` Viresh Kumar
2013-04-08 10:46 ` Rafael J. Wysocki
2013-04-08 10:41 ` Kukjin Kim
2013-04-23 15:25 ` Kukjin Kim
2013-04-23 22:59 ` Rafael J. Wysocki
2013-04-25 16:48 ` Kukjin Kim
2013-04-25 18:12 ` Rafael J. Wysocki
2013-05-13 6:05 ` Viresh Kumar
2013-05-13 10:51 ` Rafael J. Wysocki
2013-05-13 10:46 ` Viresh Kumar
2013-05-14 12:36 ` Kukjin Kim
2013-05-14 13:00 ` Rafael J. Wysocki
2013-05-20 5:29 ` Viresh Kumar
2013-05-20 13:47 ` Kukjin Kim
2013-04-08 4:54 ` Viresh Kumar
2013-04-04 12:54 ` [PATCH 08/18] cpufreq: sa11x0: " Viresh Kumar
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='CAKohpokk1Q+0gRpeW=ts0a8D+rGAUpHu62X+7ejdpfom_B6FYA@mail.gmail.com' \
--to=viresh.kumar@linaro.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 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).