new kernel developer and preparation for upstream merge

[Nelson Castillo]

On Thu, Oct 2, 2008 at 2:01 PM, Andy Green <andy at openmoko.com> wrote:
(cut)
> I think you will have more fun and progress picking a small driver from
> our tree and going through doing what is needed to improve it.
>
> If you check out the stable-tracking tree and do the Big Diff
>
> git clone git://git.openmoko.org/git/kernel.git linux-2.6
> git diff origin/master origin/stable-tracking >om-tracking.patch
> grep ^+++\  om-tracking.patch
>
> you can get an idea of everything we are carrying locally and find stuff
> that interests you that way.

Hello Andy.

I started checking the sources and I have a cleanup patch for
drivers/leds/leds-neo1973-vibrator.c.

Is the stable-tracking tree supposed to compile? (perhaps part of our
task is make it compile). I had issues with pwm.h. It seems it moved
to include/linux. I guess it has to do with the recent Linux release.

I guess I should send patches against stable-tracking after testing
that they compile (if they're cleanup patches).

Should I use another tree temporally?
What should I do?

BTW, a remark is wrong:

diff --git a/include/linux/pwm.h b/include/linux/pwm.h
index 3945f80..7c77575 100644
--- a/include/linux/pwm.h
+++ b/include/linux/pwm.h
@@ -28,4 +28,4 @@ int pwm_enable(struct pwm_device *pwm);
  */
 void pwm_disable(struct pwm_device *pwm);

-#endif /* __ASM_ARCH_PWM_H */
+#endif /* __LINUX_PWM_H */

Regards,
Nelson.-

PS: Using gmail now. I will configure mutt later for this account.
Patch might break.