ieee802154: || vs && in ieee802154_is_valid_extended_addr()

The ieee802154_is_valid_extended_addr() always returns true because
there is a typo.  The || should be &&.  Neither 0x0000000000000000ULL
nor 0xffffffffffffffffULL are valid addresses.

Signed-off-by: Dan Carpenter <[email protected]>
Acked-by: Alexander Aring <[email protected]>
Signed-off-by: Marcel Holtmann <[email protected]>

diff --git a/include/linux/ieee802154.h b/include/linux/ieee802154.h
index 5d9e7459d94b417b2929207fc8699612e01a1ce6..4c032863cd714bf4498118d42203c27e863c8b34 100644 (file)
--- a/include/linux/ieee802154.h
+++ b/include/linux/ieee802154.h
@@ -209,7 +209,7 @@ static inline bool ieee802154_is_valid_extended_addr(const __le64 addr)
         * This is currently a workaround because neighbor discovery can't
         * deal with short addresses types right now.
         */
-       return ((addr != cpu_to_le64(0x0000000000000000ULL)) ||
+       return ((addr != cpu_to_le64(0x0000000000000000ULL)) &&
                (addr != cpu_to_le64(0xffffffffffffffffULL)));
 }