>>> I think the version should have been bumped to 1.3.1 in commit
>>> d8b8a43e0f3c ('dm: fix truncated status strings', commit fd7c092e711e
>>> upstream), and that you should bump it to 1.3.2 in this patch, same as I
>>> did for 3.2.y.
>>
>> Hi, Ben
>>
>> That's true in 3.2.y.
>>
>> But in commit d8b8a43e0f3c('dm: fix truncated status strings', commit fd7c092e711e
>> upstream) for 3.4.y, there wasn't any change for the version. And is it necessary
>> to bump the version to 1.3.2 ?
>
> The situation now is:
> - Linux 3.2 had dm-mpath version 1.3.0
> - Linux 3.2.41 included the backport of 'dm: fix truncated status
> strings' and bumped the version to 1.3.1
> - Linux 3.2.54 included this fix and bumped the version to 1.3.2
> - Linux 3.4 also had dm-path version 1.3.0 (although it isn't *exactly*
> the same as the version in Linux 3.2)
> - Linux 3.4.73 included the backport of 'dm: fix truncated status
> strings', but didn't bump the version as I think it should have
>
> So dm-path labelled as version 1.3.0 may or may not include 'dm: fix
> truncated status strings'. I think it is desirable that we avoid the
> same ambiguity for versions 1.3.1 and 1.3.2.
>
Right. I will resend it later.
Thanks,
Rui
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html