diff options
| author | Oliver Hartkopp <socketcan@hartkopp.net> | 2015-11-21 17:41:21 (GMT) |
|---|---|---|
| committer | Marc Kleine-Budde <mkl@pengutronix.de> | 2015-11-23 08:37:38 (GMT) |
| commit | a2ec19f888f1fb06e2424486423a16f86ad1fcc4 (patch) | |
| tree | c1644eda37c31376d5ed54b453d2d605cc357c46 /drivers/mtd | |
| parent | ffd461f80d536336811d573f197f3e6d9872d054 (diff) | |
| download | linux-a2ec19f888f1fb06e2424486423a16f86ad1fcc4.tar.xz | |
can: remove obsolete assignment for CAN protocol error type
The assignment 'cf->data[2] |= CAN_ERR_PROT_UNSPEC' used at CAN error message
creation time is obsolete as CAN_ERR_PROT_UNSPEC is zero and cf->data[2] is
initialized with zero in alloc_can_err_skb() anyway.
So we could either assign 'cf->data[2] = CAN_ERR_PROT_UNSPEC' correctly or we
can remove the obsolete OR operation entirely.
Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net>
Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
Diffstat (limited to 'drivers/mtd')
0 files changed, 0 insertions, 0 deletions