-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Somebody in the thread at some point said: | Hi, | | Andy Green wrote: | Somebody in the thread at some point said: | | Hi, | | | | Andy Green wrote: | | Somebody in the thread at some point said: | | | Somebody in the thread at some point said: | | | | Prepare current kernel to support the new android layer | | | | | | | kernel/power/power.h | 31 +- | | | | kernel/power/process.c | 28 +- | | | | | | Hi Michael - | | | | | | It seems we are missing some pre-patch on kernel/power/process.c, | | | because the patch here does not apply on there (not due to 2.6.29-rc2 | | | uplevel either). | | | | Another issue seems to be stuff has moved into this new drivers/staging | | place in 2.6.29. There seems to be some android stuff in there already | | (./drivers/staging/android) we will need to be compatible with. | | | | -Andy | |> | | As I suppose they move in a directory, so I just patch on that? I have | | few diff. | | Yes if you can patch against the upstream state in | ./drivers/staging/android I think it will be easier. | | If you can also make a patch to destroy our old tree in | ./drivers/android cleanly that'd reduce confusion too. | | If we can keep everything in ./drivers/staging/android then I can diff | that directory when I rebase from upstream and hopefully it won't be a | big mess. | | -Andy |> | Well, | I'm agree with you. I rebase all on the new directory. It is possible to | create a | android-kernel branch in the openmoko?
It's possible but why do we need it? I can carry this in andy-tracking directly. - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmAUfEACgkQOjLpvpq7dMrkcwCeJ2In8PlCx6v2QQXJ9X20PH2D Mu4AoIhIr7xvLUSv6O0lxLLCdmIR4J7e =kUvt -----END PGP SIGNATURE-----
