here is the patch that fixes the bug introduced by my previous patch which
already went into 2.6.12-rc2 and is likely to cause trouble is someone hits
one the else case here by accident.

Using the &= operation before the if statement destroys the information the
if asks for so we always go into the else branch.
Signed-off-by: NRolf Eike Beer <eike-hotplug@sf-tec.de>
Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>