10/10/2017 16:15, Hemant Agrawal: > Signed-off-by: Hemant Agrawal <hemant.agra...@nxp.com> > --- > drivers/bus/fslmc/Makefile | 3 ++- > drivers/crypto/dpaa2_sec/Makefile | 3 ++- > drivers/event/dpaa2/Makefile | 3 ++- > drivers/mempool/dpaa2/Makefile | 3 ++- > drivers/net/dpaa2/Makefile | 3 ++- > 5 files changed, 10 insertions(+), 5 deletions(-)
Why are you changing LIBABIVER in all these libs? Generally speaking, a driver should not upgrade its ABI version, because it should have no interface. The ABI version must be changed in the patch breaking the ABI. If you do it later, it must be a fix with Fixes line. This way we will have the reference to the code breaking the ABI.
