|author||Luis R. Rodriguez <firstname.lastname@example.org>||2012-11-29 17:27:25 -0800|
|committer||Luis R. Rodriguez <email@example.com>||2012-11-29 17:39:13 -0800|
compat-drivers: move all patch types under patches/
The number of patch directories for the different life cycle a patch can be on its way upstream had reached 4: * pending-stable * linux-next-pending * linux-next-cherry-picks * crap Apart from this we also had the backport related patches. In the future I see potential for other directories for different categories of patches. Consider how we are breaking down the backport patches into specific documented collateral evolutions and of those type of collateral evolutions there may be different types of collateral evolutions which we could likely treat / document differently. Another type of patch that I forsee us having to deal with are patches for drivers that are not upstrea -- like crap, but for drivers in a unified driver tree that is *designed* from scratch to be targetting upstream Linux inclusion using the same coccinelle technology I forsee us using for backporting collateral evolutions. Since the number of patch directories can get out of hand at the top level lets just stuff then all under patches/ and deal with patches there. This also places the backport patches into a directory called collateral-evolutions/ to help promote and educate on the nature of the changes that we have to deal with when backporting. Cc: Julia Lawall <firstname.lastname@example.org> Cc: Adrian Chadd <email@example.com> Signed-off-by: Luis R. Rodriguez <firstname.lastname@example.org>
Diffstat (limited to 'patches/collateral-evolutions/README')
1 files changed, 16 insertions, 0 deletions
diff --git a/patches/collateral-evolutions/README b/patches/collateral-evolutions/README
new file mode 100644
@@ -0,0 +1,16 @@
+compat-drivers collateral evolutions patches
+You must have a really good reason to be adding files
+in this directory. Your reasoning should either match the
+explanation already present on the top of each patch file
+or you should add your own.
+We try to avoid having patch files because:
+ * Its a pain in the ass to maintain them.
+ * Most backport changes can be pulled off through
+ some macro magic or new files which implement
+ the new functionality on the old kernels.