[Prism54-devel] Prism54 in 2.6.4-bk2

[Marcel Holtmann]

Hi Luis,

> Hmm. Now what? Should we create a new set of automated patchsets against the latest kernel
> snapshot? Or just not worry about that and keep on happilly with our stable kernel
> patches?
> 
> The prism54 driver snapshot that went into bk2 could be marked as our
> first testing snapshot... If so, we could also start a new ChangeLog.

actually I propose that you only develop on base of 2.6 and send a bunch
of updates to Jeff for every 2.6 release. Mark them as unstable/testing
and stable so they go into -mm for further testing or directly into the
next 2.6 release for a wide end user testing. And from time to time you
should backport these changes for 2.4 kernels, but you really need to
have different CVS repositories for the two kernel series. Maybe a
compat24.[ch] for the things that are different. The 2.6 driver should
get the main focus and it should be free of #ifdef's.

The ChangeLog itself is not so important, but you should have a version
string in your kernel module, so you can identify problematic versions
and compare this with your changes. Maybe something like this

	#define VERSION "1.0"

	MODULE_VERSION(VERSION);

and modinfo shows the version number.

Looking at bkbits.net and starting with Bitkeeper is maybe a good idea.

Regards

Marcel