On 08/30/10 20:27, Anthony Liguori wrote: > On 08/30/2010 01:19 PM, Jes Sorensen wrote: >> >> I totally agree on this. The problem with having such arguments passed >> in is that you never know if they were used in the past and it was >> forgotten when the code using them was removed, or if it's new code, in >> which case they do deserve the extra scrutiny. >> > > Or, we exercise common sense instead of blinding removing arguments just > because a certain uncommon warning mode of GCC complains.
Before making the change, I did indeed look at the code for a while, considering whether it was reasonable to leave the unused variable in place. However I don't see anything in there that makes it likely that the block state parameter is going to be used in that function in the near future, if at all. If you feel so strongly about it, then lets apply the __unused attribute as Richard suggested so it's clear that that argument was added on purpose. Jes
