On Mon, 9 Feb 2015 21:52:21 -0200 Gustavo Bittencourt <gbitten@xxxxxxxxx> wrote: > This is probably a silly question. I noticed that the below commits > revert each other. Is any reason to maintain those commits in recent > releases? The rebase release is just that: a rebase. If a revert exists, but does not cause any issue during the rebase, there's no reason to remove it. I have (in fact in the last release I did) removed commits that later get reverted. But that's because the original commit conflicts with a new stable release, and then there's a reason to remove it. -- Steve > > commit: migrate_disable pushd down in atomic_dec_and_spin_lock > 9056f04da7fd3bd39d5bc05cb42cf9d0f5b7b98c > https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit/?h=v3.14-rt-rebase&id=9056f04da7fd3bd39d5bc05cb42cf9d0f5b7b98c > > commit: Revert "migrate_disable pushd down in atomic_dec_and_spin_lock" > 2137b9fff666c62077c7ae35e865eec86da0a499 > https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit/?h=v3.14-rt-rebase&id=2137b9fff666c62077c7ae35e865eec86da0a499 -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html