All,
I've taken the ill-fated merge attempt from a few weeks ago and have reworked it into 16 smaller, logical patches. I've also made certain that in the end, when all patches are applied all of the touched boards will build.
Each patch I submit will consist of a brief description of what was changed and why, as well as a diffstat and the patch itself.
I'll start submitting the diffs for review.
--jason--
Jason Schildt jschildt@lnxi.com writes:
All,
I've taken the ill-fated merge attempt from a few weeks ago and have reworked it into 16 smaller, logical patches. I've also made certain that in the end, when all patches are applied all of the touched boards will build.
Each patch I submit will consist of a brief description of what was changed and why, as well as a diffstat and the patch itself.
As a bit of constructive criticism, the why the change was missing on quite a few of the diffs. With the why missing it is hard for other people to understand the problem and comment effectively.
Eric
Jason Schildt jschildt@lnxi.com writes:
All,
I've taken the ill-fated merge attempt from a few weeks ago and have reworked it into 16 smaller, logical patches. I've also made certain that in the end, when all patches are applied all of the touched boards will build.
Each patch I submit will consist of a brief description of what was changed and why, as well as a diffstat and the patch itself.
I'll start submitting the diffs for review.
Next time please include in the subject a very brief summary of what the patch is doing not just the patch count.
Something like: [PATCH 4/16] Dual core and E0 changes. [PATCH 13/16] auto.c and failover.c changes.
Some kind of logical name for each patchset, so they can be thought of and referred to more easily.
Eric