Re: [PATCH V3] scripts: objdiff: detect object code changes between two commits

[Michal Marek]

On Mon, Apr 07, 2014 at 06:30:29PM +0000, Jason Cooper wrote:
> objdiff is useful when doing large code cleanups.  For example, when
> removing checkpatch warnings and errors from new drivers in the staging
> tree.
> 
> objdiff can be used in conjunction with a git rebase to confirm that
> each commit made no changes to the resulting object code.  It has the
> same return values as diff(1).
> 
> This was written specifically to support adding the skein and threefish
> cryto drivers to the staging tree.  I needed a programmatic way to
> confirm that commits changing >90% of the lines didn't inadvertently
> change the code.
> 
> Temporary files (objdump output) are stored in
> 
>   /path/to/linux/.tmp_objdiff
> 
> 'make mrproper' will remove this directory.
> 
> Signed-off-by: Jason Cooper <jason@xxxxxxxxxxxxxx>
> ---
> Changes from V2:
> 
>  - use /path/to/linux/.tmp_objdiff instead of /tmp/objdiff (Michal Marek)
> 
>  - don't delete object files during record (Michal Marek)
> 
>  - remove .tmp_objdiff directory during 'make mrproper' (Michal Marek)

Applied to kbuild.git#misc, thanks.

Michal
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/