treewide: remove "+" sign for increment with macaddr_add
Many people appear to use an unneeded "+" prefix for the increment
when calculating a MAC address with macaddr_add. Since this is not
required and used inconsistently [*], just remove it.
[*] As a funny side-fact, copy-pasting has led to almost all
hotplug.d files using the "+", while nearly all of the
02_network files are not using it.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
This commit is contained in:
@@ -10,7 +10,7 @@ case "$FIRMWARE" in
|
||||
case $board in
|
||||
bt,homehub-v5a)
|
||||
caldata_extract_ubi "caldata" 0x5000 0x844
|
||||
ath10k_patch_mac $(macaddr_add $(mtd_get_mac_binary_ubi caldata 0x110c) +3)
|
||||
ath10k_patch_mac $(macaddr_add $(mtd_get_mac_binary_ubi caldata 0x110c) 3)
|
||||
;;
|
||||
*)
|
||||
caldata_die "board $board is not supported yet"
|
||||
|
||||
@@ -29,7 +29,7 @@ case "$FIRMWARE" in
|
||||
;;
|
||||
bt,homehub-v5a)
|
||||
caldata_extract_ubi "caldata" 0x1000 0x1000
|
||||
ath9k_patch_mac_crc $(macaddr_add $(mtd_get_mac_binary_ubi caldata 0x110c) +2) 0x10c
|
||||
ath9k_patch_mac_crc $(macaddr_add $(mtd_get_mac_binary_ubi caldata 0x110c) 2) 0x10c
|
||||
;;
|
||||
tplink,tdw8970|\
|
||||
tplink,tdw8980)
|
||||
|
||||
@@ -39,11 +39,11 @@ case "$FIRMWARE" in
|
||||
;;
|
||||
bt,homehub-v3a)
|
||||
caldata_extract_swap "art-copy" 0x0 0x1000
|
||||
ath9k_patch_mac_crc $(macaddr_add $(mtd_get_mac_ascii u-boot-env ethaddr) +2) 0x10c
|
||||
ath9k_patch_mac_crc $(macaddr_add $(mtd_get_mac_ascii u-boot-env ethaddr) 2) 0x10c
|
||||
;;
|
||||
netgear,dgn3500|netgear,dgn3500b)
|
||||
caldata_extract "calibration" 0xf000 0x1000
|
||||
ath9k_patch_mac_crc $(macaddr_add $(mtd_get_mac_ascii u-boot-env ethaddr) +2) 0x20c
|
||||
ath9k_patch_mac_crc $(macaddr_add $(mtd_get_mac_ascii u-boot-env ethaddr) 2) 0x20c
|
||||
;;
|
||||
avm,fritz7312|avm,fritz7320)
|
||||
caldata_extract "urlader" 0x985 0x1000
|
||||
|
||||
Reference in New Issue
Block a user