Make sparse warn about initializers that initialize the same member twice
commit27ff96a96c95d0171f3215458dd5a2ebc4bfafbf
authorLinus Torvalds <torvalds@g5.osdl.org>
Sun, 3 Sep 2006 19:32:31 +0000 (3 12:32 -0700)
committerLinus Torvalds <torvalds@g5.osdl.org>
Sun, 3 Sep 2006 19:32:31 +0000 (3 12:32 -0700)
tree8d64cfc6f11e29159c033073e63fd4a9baf94776
parent37475a6c1c3e66219e68d912d5eb833f4098fd72
Make sparse warn about initializers that initialize the same member twice

Surprisingly, gcc apparently doesn't warn/notice.  And yes, we had at
least one such error in the kernel due to some over-eager cut-and-paste
happening.

[ Side note: this should also fix a problem with bitfields at byte
  offset zero not necessarily getting sorted right.  Not that that would
  have likely affected any current usage of sparse.  ]

Signed-off-by: Linus Torvalds <torvalds@osdl.org>
expand.c