new kernel developer and preparation for upstream merge

[Andy Green]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Somebody in the thread at some point said:
| On Fri, Sep 19, 2008 at 7:44 AM, Werner Almesberger
<werner at openmoko.org> wrote:
|> Balaji Rao is joining Openmoko as a new kernel developer who will help
|> with the upstream merge. Welcome, Balaji !
|
| Hello Werner, Andy, Balaji and friends :-)
|
| I'd love to start helping you with this effort. I've developed basic
| drivers before and I hope to learn a lot of things soon (advanced git,
| how to manage lots of patches, openmoko drivers). I wonder what is the
| best way to get started (I will have a few hours (2 <= hours <= 5 )
| per day this month).
|
| The following task seems good to get started. What do you think?
|
| What I like from this task is that I will get familiar with the
| Openmoko-specific kernel options and when something doesn't compile I
| will start exploring the  code, finding out why things break and so
| on.
|
|> - make sure the code still compiles if individual config options are
|>  disables or enable. I'd suggest to try all our options, none of our
|>  options, walk through the list of out options and enable/disable
|>  them one at a time, and finally try random combinations. This
|>  should be automated, of course.

Thanks for considering to spend the time.

There actually is a

make randconfig

in the mainline Makefile already FWIW.

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.

- -Andy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkjlGmUACgkQOjLpvpq7dMrSHgCfcavlLldpuHi778/ZBbGhOUCN
P+4AnRgB5X84M8W4/nl4v0dXOjU2H1ix
=cfRD
-----END PGP SIGNATURE-----