From: anarsoul@gmail.com (Vasily Khoruzhick)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] s3c244x: Fix compilation issue due to moved cpufreq-related files
Date: Fri, 5 Mar 2010 09:04:09 +0200 [thread overview]
Message-ID: <201003050904.27297.anarsoul@gmail.com> (raw)
In-Reply-To: <20100304232006.GA31126@trinity.fluff.org>
? ????????? ?? 5 ????? 2010 01:20:06 ????? Ben Dooks ???????:
> I've fixed this by moving the files instead of hte makefile. Commit will
> be in next-samsung soon. Thanks for pointing this out.
Sorry, but it seems you forgot about s3c2440-cpufreq.c in commit 8997de30ad
(look at my patch again :)). Please move it from plat-s3c244x to arch-s3c2440
too.
Regards,
Vasily
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100305/79aa97f0/attachment.sig>
prev parent reply other threads:[~2010-03-05 7:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 14:38 [PATCH] s3c244x: Fix compilation issue due to moved cpufreq-related files Vasily Khoruzhick
2010-03-04 23:20 ` Ben Dooks
2010-03-05 7:04 ` Vasily Khoruzhick [this message]
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=201003050904.27297.anarsoul@gmail.com \
--to=anarsoul@gmail.com \
--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).