| <?xml version="1.0" encoding="utf-8"?><manifest revision="667f8630a76f256e07a55942bd493afa00835346"> |
| <notice>Your sources have been sync'd successfully.</notice> |
| <remote alias="cros" fetch="https://chromium.googlesource.com/" name="chromium"/> |
| <remote fetch="https://chromium.googlesource.com" name="cros" review="https://chromium-review.googlesource.com"/> |
| <default remote="cros" revision="refs/heads/master" sync-j="8"/> |
| <project name="chromium/deps/libmtp" path="chromium/src/third_party/libmtp" revision="0680a2d0c4cec58f8163fe115de80cff8852fd8b" upstream="refs/heads/master"/> |
| <project name="chromium/src/third_party/hwcplus" revision="e66a31e54e12906e86dc59f95b458889f025c505" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk,buildtools" name="chromium/tools/depot_tools" revision="b6795643ec0305ba2ff862fcd0f450756aa5e58c"/> |
| <project groups="minilayout,project_sdk,buildtools" name="chromiumos/chromite" path="chromite" revision="1e46be8f4940e2ea52adf09184362e5548440526" upstream="refs/heads/master"> |
| <copyfile dest="AUTHORS" src="AUTHORS"/> |
| <copyfile dest="LICENSE" src="LICENSE"/> |
| </project> |
| <project name="chromiumos/manifest" path="manifest" revision="60d0de0f26feea2c8c63895e576990cc21115c17" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk" name="chromiumos/overlays/board-overlays" path="src/overlays" revision="5841ff1ab544561fc675cd93456aed9153ea2ab1" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk" name="chromiumos/overlays/chromiumos-overlay" path="src/third_party/chromiumos-overlay" revision="076a87fd993cb604852587817ab023f9a188404d" sync-c="true" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk" name="chromiumos/overlays/eclass-overlay" path="src/third_party/eclass-overlay" revision="475609d0d82476d9162498e238df000eed27ff36" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk" name="chromiumos/overlays/portage-stable" path="src/third_party/portage-stable" revision="f21c9ee135e8b46016083f644c75ff115db6446b" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/assets" path="src/platform/assets" revision="48950c9cb35671c59f9f63316683357c8792b79d" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/audiotest" path="src/platform/audiotest" revision="3fb17a505c9dae6dbac84c98f8cd8f30941b6eef" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/battery_updater" path="src/platform/battery_updater" revision="32463c6de8e8c98d4b1711937bc7678afc121a85" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/bootcache" path="src/platform/bootcache" revision="ebe3a0995e90026433ffc62b7aeed6cad1f28694" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/btsocket" path="src/platform/btsocket" revision="1b65449a647c99556511df30b8ab660b98acce7f" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/chameleon" path="src/platform/chameleon" revision="06e2b418bd604b362d3c245562a068f619b2b1bf" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/chromiumos-assets" path="src/platform/chromiumos-assets" revision="05ce8d3c59a2d8e765b3beb2e1a69e7fcf59e5ba" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk,buildtools" name="chromiumos/platform/crostestutils" path="src/platform/crostestutils" revision="c0ed34f476aeecf52ac9bfea4750ac4fb8a539c4" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk,buildtools" name="chromiumos/platform/crosutils" path="src/scripts" revision="948dba96f358f9da6baaf28cba2f6969d7db2de9" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/depthcharge" path="src/platform/depthcharge" revision="d3ee2dca06f4ad24bb69fb6500c23a2391533ec8" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk,buildtools" name="chromiumos/platform/dev-util" path="src/platform/dev" revision="ba4e00f161e55bd7967e154aba7755f96470e935" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/dm-verity" path="src/platform/verity" revision="c4df284b32558f631862f79c75fc03af4f5ca68a" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/drm-tests" path="src/platform/drm-tests" revision="987a60f5ae48541c1df1aab8a01560446b712f76" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/ec" path="src/platform/ec" revision="813e56e10af48dc010dc629cb6d0c37efcb995dd" upstream="refs/heads/master"/> |
| <project groups="project_sdk" name="chromiumos/platform/factory" path="src/platform/factory" revision="190aa4addbc9a286ace2aaaba0401a91a48700c9" upstream="refs/heads/master"/> |
| <project groups="project_sdk" name="chromiumos/platform/factory_installer" path="src/platform/factory_installer" revision="f90b5268a73704d68700a782d170261d546fd85a" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/firmware" path="src/platform/firmware" revision="8b14a26ccaaac20c33535a38199273c0acecb33f" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/frecon" path="src/platform/frecon" revision="38917fe2b121610c487570bb41f97167a76132ce" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/gestures" path="src/platform/gestures" revision="05325e18158f8519f853e086e92c04504e2b87aa" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/glbench/images" path="src/platform2/glbench/images" revision="5fd5ce655833f65d46b1950bec4eedeb4e96959b" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/go-seccomp" path="src/platform/go-seccomp" revision="0280326e5bd212fcfbe3696e113730045debae74" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/google-breakpad" path="src/platform/google-breakpad" revision="cf5b98e801bcf0218dfe19ac722c5fa600814678" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/initramfs" path="src/platform/initramfs" revision="7efff0e164437b46def2b2f556d822827e29a0be" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/inputcontrol" path="src/platform/inputcontrol" revision="ae0b15dc322bab9bf6d7c4fcd5f77d488766a275" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/jabra_vold" path="src/platform/jabra_vold" revision="5ee665e7c68856d3b6ce8bb0f610d43503e603af" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/libevdev" path="src/platform/libevdev" revision="61f882f395b9f39478d7164209e7134cccdcb72b" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/memento_softwareupdate" path="src/platform/memento_softwareupdate" revision="0b6e7be80034cbede5e111108c46bb75bb5942dd" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/microbenchmark" path="src/platform/microbenchmark" revision="d5ea30febe406c5b486325dfae926564f3a46efd" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/minigbm" path="src/platform/minigbm" revision="dc94b474288cec3c8c9ca55e0f0b5ee2d681f2e7" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/monitor_reconfig" path="src/platform/monitor_reconfig" revision="c02c806dfe581dcff530f75f7b73847f7c3dc229" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/mosys" path="src/platform/mosys" revision="46479afc8eb9d0801e2ee066ec6b1842d8ab8290" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/mtpd" path="src/platform/mtpd" revision="9f9c6bf080b3f75f6249fadf62aeb9591a1915a4" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/mtplot" path="src/platform/mtplot" revision="5e4f631e633384751f582bd9db5f4d6eb2112494" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/mttools" path="src/platform/mttools" revision="7cde658e97d6a00cf0d43f0478544e71ffd2e2d2" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/punybench" path="src/platform/punybench" revision="5a230ee17756dc43ff732932dcb52899c06a4d09" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/system_api" path="src/platform/system_api" revision="e1517ab9becc2b8525a4352943febc794d107b7f" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/touch_firmware_test" path="src/platform/touch_firmware_test" revision="9ce13ccbf099a9c5c3c7d54f2f8e445bb711c114" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/touch_noise_filter" path="src/platform/touch_noise_filter" revision="322345ed0b1ab6e42ec2710ef5c904464b0dc218" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/touch_updater" path="src/platform/touch_updater" revision="abbaca628034dc25bca7f8a6c0015a8c21154d10" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/touchbot" path="src/platform/touchbot" revision="c3c6ea92a02cb6bba18175c713cdedec18309d28" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/touchpad-tests" path="src/platform/touchpad-tests" revision="35468240e94dd74577f06dbeca5aac88e4c0b8ef" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/tpm" path="src/third_party/tpm" revision="0cba6cadd1bea1ce3717779201d594c4c9131dc2" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/tpm_lite" path="src/platform/tpm_lite" revision="066c7f963b3ef733716251b666e0af0afd03b4fe" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/trunks" path="src/platform/trunks" revision="03382e68603e99b0fdc81e2f3500448c47ba2396" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/uboot-env" path="src/platform/uboot-env" revision="108ebbfac4d13d11e1940216434c368384ee0c0b" upstream="refs/heads/master"/> |
| <project groups="buildtools" name="chromiumos/platform/vboot_reference" path="src/platform/vboot_reference" revision="b491bc8bb1499452536eb140c22f749d1c9f9fc3" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/vpd" path="src/platform/vpd" revision="f07e3dfe1be57bc778d84657bf051ff50443cf56" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/webplot" path="src/platform/webplot" revision="bbd5ea22ef9f8e109e363b26958d9a2fc8921f0f" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/wireless_automation" path="src/platform/wireless_automation" revision="d7177dbd464f2952e10309bf1eef56bb31a7f8ad" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/workarounds" path="src/platform/workarounds" revision="48a42e96e26edd12bf295ea13b50bcdd40c068e3" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/xf86-input-cmt" path="src/platform/xf86-input-cmt" revision="3f2ffc921952e57a4343463b0679d90b80b51fc7" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/xorg-conf" path="src/platform/xorg-conf" revision="2389885e788815f7d44b6cd3160c4085da7e689e" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform2" path="src/platform2" revision="ecb08355b44f255feb0bdaa0d19ab2af56c0df4b" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk,buildtools" name="chromiumos/repohooks" path="src/repohooks" revision="81d07144f3790a66819ecd320101bfdf51dd15f8" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/adhd" path="src/third_party/adhd" revision="bc573a33370cf0a323cb7c5dd4fe2956a0141e2f" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/android_mtdutils" path="src/third_party/android_mtdutils" revision="9bcfc3ee238f16925e9aaa4573129784ebb397e7" upstream="chromeos"/> |
| <project name="chromiumos/third_party/arm-trusted-firmware" path="src/third_party/arm-trusted-firmware" revision="f57e2db6ef4b86a6af57891a2d7a90266ad6c033" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/atheros" path="src/third_party/atheros" revision="52a5bdaa8930c14ee42518354de3e5ec09911c6b" upstream="refs/heads/master"/> |
| <project groups="buildtools" name="chromiumos/third_party/autotest" path="src/third_party/autotest/files" revision="76bed2f01aae6332e888faae6bc1f36dedb12de6" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/binutils" path="src/third_party/binutils" revision="ff847b57d425687df548c860b48851f090bd79e2" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/bluez" path="src/third_party/bluez" revision="3cc29b0281e14f1bb5b36e9a569c663cc54db970" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/bootstub" path="src/third_party/bootstub" revision="5ac54e8d3d305c2c6c7297e8e54d3cf7e4629b29" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/broadcom" path="src/third_party/broadcom" revision="4070e7161f2f1a1a22027a744eb868500688f0b6" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/bsdiff" path="src/third_party/bsdiff" revision="8c17bdc0d759c8e6da90c5f72b052ba2605a0a3a" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/cbootimage" path="src/third_party/cbootimage" revision="b7d5b2d6a6dd05874d86ee900ff441d261f9034c" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/chrontel" path="src/third_party/chrontel" revision="7bcd0328d0eeef6a0539bd0ba80cd9a545e6cf4a" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/coreboot" path="src/third_party/coreboot" revision="07cb719caf40b59c5519fcf212c2fb50f006812e" upstream="refs/heads/chromeos-2015.07"/> |
| <project name="chromiumos/third_party/coreboot/blobs" path="src/third_party/coreboot/3rdparty/blobs" revision="612cd24575ab8bb77260e22f3665f46b77794ffe" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/cypress-tools" path="src/third_party/cypress-tools" revision="043fba1c35f89cce95f804bf6d4f01cfc23a6c21" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/daisydog" path="src/third_party/daisydog" revision="3182aa85c087446e4358370549adc45db21ec124" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/dbus-cplusplus" path="src/third_party/dbus-c++" revision="f140c0aa430e1db1c0f31d23d3eb2397d47f209e" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/dbus-spy" path="src/third_party/dbus-spy" revision="0e04421c73b24536de7fcc1886da469d8b7a2a41" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk,buildtools" name="chromiumos/third_party/dpkt" path="chromite/third_party/dpkt" revision="f5259728b1294412bee945df9708efba09ea9160"> |
| <annotation name="branch-mode" value="pin"/> |
| </project> |
| <project name="chromiumos/third_party/edk2" path="src/third_party/edk2" revision="0aa39d284043be61b5f1222afdffd39a5abaf3aa" upstream="refs/heads/chromeos-2014.04"/> |
| <project name="chromiumos/third_party/em100" path="src/third_party/em100" revision="6e60dbae5bf62cd0ffffb9fc5ca9ba93e831ee88" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/flashmap" path="src/third_party/flashmap" revision="aaaf66654dba797f152066df4d1dc4144b492c66" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/flashrom" path="src/third_party/flashrom" revision="96c67aab12f53380342a6eeabf8954eac02a7911" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/gcc" path="src/third_party/gcc" revision="b6125c702850488ac3bfb1079ae5c9db89989406" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk,buildtools" name="chromiumos/third_party/gdata" path="chromite/third_party/gdata" revision="fe7e5c90a9827feb66ed446b2d297a1618b25272" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/gdmwimax" path="src/third_party/gdmwimax" revision="e8236b4b2d66b1972e4f84955a238134acd7f6a1" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/gobi3k-sdk" path="src/third_party/gobi3k-sdk" revision="69702c400e274984a24d08fcaefe3952d5dcb36e" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/grub2" path="src/third_party/grub2" revision="df6034c59cb2d847f9e780cf2def30c5c9b8305f" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/hdctools" path="src/third_party/hdctools" revision="3703700655a062ba9f4a5ba30af2208636d5eb09" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/hostap" path="src/third_party/wpa_supplicant" revision="88126a88e240ab18730163ea0f5d0b775247ac23" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/hwcplus-drm" path="src/third_party/hwcplus-drm" revision="7376a8da1c961115a61d7a3cb23bb13e4153583d" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/ibus-chewing" path="src/third_party/ibus-chewing/files" revision="7a9514a0844eb5eb90ab96f62484a6af9e4a0d6d" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/ibus-xkb-layouts" path="src/third_party/ibus-xkb-layouts/files" revision="6af015110aa92dc2eed88a9f704634c3eff53b14" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v3.8" revision="f40dc81315226652baad6bd18d1b515597a95b5a" upstream="refs/heads/chromeos-3.8"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v3.10" revision="d200a34f72072cd531f08bba1b5d7e32d6b65e7a" upstream="refs/heads/chromeos-3.10"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v3.14" revision="704e259561befee796c3ba0a951f3a1d5da1b4ba" upstream="refs/heads/chromeos-3.14"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v3.18" revision="bcb8e68962488fbdbdf7bc3d38a419ce68f4c926" upstream="refs/heads/chromeos-3.18"/> |
| <project name="chromiumos/third_party/khronos" path="src/third_party/khronos" revision="c4932bd57b6edfc42773b4527180a219b9af9ca4" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libc-bench" path="src/third_party/libc-bench" revision="76793dd4b09191a78a78180012718e72d792717f" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libmbim" path="src/third_party/libmbim" revision="c4e2949edeed01ca3b810729a7af0d265c49629b" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libqmi" path="src/third_party/libqmi" revision="a436c551cf226af66cdb3dd74ee3971d0b1dae04" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libresample" path="src/third_party/libresample" revision="cc9f20f439396b7d45e94b8301edd95d33f26a46" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libscrypt" path="src/third_party/libscrypt" revision="b45c53f9418a6eff2c8ed98703a55f96029304b1" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libsigrok" path="src/third_party/libsigrok" revision="199fe31115c76231746f5953271795d58679561c" upstream="refs/heads/chromeos"/> |
| <project name="chromiumos/third_party/libsigrok-cli" path="src/third_party/sigrok-cli" revision="c9edfa218e5a5972531b6f4a3ece8d33a44ae1b5" upstream="refs/heads/chromeos"/> |
| <project name="chromiumos/third_party/libsigrokdecode" path="src/third_party/libsigrokdecode" revision="3279c2825684c7009775b731d0a9e37815778282" upstream="refs/heads/chromeos"/> |
| <project name="chromiumos/third_party/libv4lplugins" path="src/third_party/libv4lplugins" revision="07f7a81118f74a8a7bc4ef5b81ee651aa12b8adb" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/linux-firmware" path="src/third_party/linux-firmware" revision="0ece365f95c0b1a81dc9b768504c5994202798c8" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/ltp" path="src/third_party/ltp" revision="4290bd545748cae9e3abad8113dcf4f6dc82e840" upstream="refs/heads/chromeos-20150119"/> |
| <project name="chromiumos/third_party/marvell" path="src/third_party/marvell" revision="f1684f7174aad3f4249416a3e9049899d05824ba" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/memtest" path="src/third_party/memtest" revision="3d4be6e3bfd819856e38a82e35c206fec4551851" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/mesa" path="src/third_party/mesa" revision="c2a0600d5b0645533ba442b5ab879b23c2564a4d" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/mesa" path="src/third_party/mesa-img" revision="129178893b2260df22db96327c5ca9c2ce7db046" upstream="refs/heads/mesa-img"/> |
| <project name="chromiumos/third_party/minifakedns" path="src/third_party/miniFakeDns" revision="6184bea119dea53da539727fe8c2a116f98cef24" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/mmc-utils" path="src/third_party/mmc-utils" revision="c2faa3df83d679cb01b553d567b16ecc2299f134" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/modemmanager-next" path="src/third_party/modemmanager-next" revision="52fbe37e5d78011366eec0033d5374a0c8950f0e" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/opencryptoki" path="src/third_party/opencryptoki" revision="b67690aeeb4174b2253db18a9c1b19eeb219a4ef" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/ply-image" path="src/third_party/ply-image" revision="7d5367e2a8618718e90274ae920bc6f406b59b9e" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk,buildtools" name="chromiumos/third_party/pyelftools" path="chromite/third_party/pyelftools" revision="19b3e610c86fcadb837d252c794cb5e8008826ae" upstream="refs/heads/master-0.22"/> |
| <project groups="project_sdk" name="chromiumos/third_party/rootdev" path="src/third_party/rootdev" revision="5d7d7ff513315abd103d0c95e92ae646c1a7688c" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/seabios" path="src/third_party/seabios" revision="3004147dd3707e600772ec6c5d37beac7f4b8eb4" upstream="refs/heads/chromeos-2014.11.03"/> |
| <project name="chromiumos/third_party/sysbios" path="src/third_party/sysbios" revision="33e1db34b8162de72a5e9bbbc44e6bce38978396" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/tegra-power-query" path="src/third_party/tegra-power-query" revision="66f1f0d949f4ca4836c1a65b622629205240e37a" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/tegrastats" path="src/third_party/tegrastats" revision="1be161a89525d840e1f6d1f21b3f45645a7dedb3" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/tlsdate" path="src/third_party/tlsdate" revision="ab36a75379f1cfaa7a803cb6f8b33ad31e49fcbf" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/tpm-emulator" path="src/third_party/tpm-emulator" revision="310a21ef24ace14b4d6e8095172445494f54ff25" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/tpm2" path="src/third_party/tpm2" revision="a49f9129735985d8851e38da0f2ca4380a51e388" upstream="refs/heads/master"/> |
| <project groups="project_sdk" name="chromiumos/third_party/trousers" path="src/third_party/trousers" revision="4ca78880022107e61481a0e2e053acc82b2e5090" upstream="refs/heads/master-0.3.13"/> |
| <project name="chromiumos/third_party/u-boot" path="src/third_party/u-boot/files" revision="b6e27ea40d24cd4273143eeab741a39704ee47fe" upstream="refs/heads/chromeos-v2013.06"/> |
| <project name="chromiumos/third_party/u-boot" path="src/third_party/u-boot/next" revision="04cfc2000cdc6a27b8a33e3b112e97c33e22f318" upstream="refs/heads/chromeos-v2015.07-rc1"/> |
| <project name="chromiumos/third_party/xf86-video-armsoc" path="src/third_party/xf86-video-armsoc" revision="30370e9dbf7ba0e457ee7de297d2ad6c269a00be" upstream="refs/heads/master"/> |
| <project groups="minilayout,project_sdk,buildtools" name="external/swarming.client" path="chromite/third_party/swarming.client" revision="0ec868bc7a6a72ca40e3cb508898e4e07f109ae1"/> |
| <repo-hooks enabled-list="pre-upload" in-project="chromiumos/repohooks"/> |
| <pending_commit branch="chromeos-3.14" change_id="Ibab75366fe3aa7120cb780c68f1e90683531c01b" commit="8eebc662fbb5d8bcb690dec721e0822f280b11b8" commit_message="ath9k_htc: wmi: match wait_for_completion_timeout return type Return type of wait_for_completion_timeout is unsigned long not int. As time_left is exclusively used for wait_for_completion_timeout here its type is simply changed to unsigned long. API conformance testing for completions with coccinelle spatches are being used to locate API usage inconsistencies: ./drivers/net/wireless-4.2/ath/ath9k/wmi.c:331 int return assigned to unsigned long Patch was compile tested with x86_64_defconfig + CONFIG_ATH_CARDS=m, CONFIG_ATH9K_HTC=m Patch is against 4.1-rc3 (localversion-next is -next-20150514) Signed-off-by: Nicholas Mc Guire <hofrat@osadl.org> Signed-off-by: Kalle Valo <kvalo@codeaurora.org> (cherry picked from commit 61fc39204bc0db0070267fe0f7920c38b0af87ef) TEST=none BUG=none Change-Id: Ibab75366fe3aa7120cb780c68f1e90683531c01b Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307350 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="0" gerrit_number="307350" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/50/307350/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="If7ef9031eabf7f8136f77d59a46ec3c9247ef407" commit="8be029fcf2c0a77fc8cb47e9fa7c1f975803b93b" commit_message="UPSTREAM: ath9k: match wait_for_completion_timeout return type Return type of wait_for_completion_timeout is unsigned long not int. As time_left is exclusively used for wait_for_completion_timeout here its type is simply changed to unsigned long. API conformance testing for completions with coccinelle spatches are being used to locate API usage inconsistencies: ./drivers/net/wireless-4.2/ath/ath9k/link.c:197 int return assigned to unsigned long Patch was compile tested with x86_64_defconfig + CONFIG_ATH_CARDS=m, Patch is against 4.1-rc3 (localversion-next is -next-20150514) Signed-off-by: Nicholas Mc Guire <hofrat@osadl.org> Signed-off-by: Kalle Valo <kvalo@codeaurora.org> (cherry picked from commit ab63cb8b0cc84a89f65e418357d7e6b9b914c89a) TEST=none BUG=none Change-Id: If7ef9031eabf7f8136f77d59a46ec3c9247ef407 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307351 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="0" gerrit_number="307351" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/51/307351/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I97d68782d7362d94d41b28561a156b0ac30c34b1" commit="446045a1b0abeb1d4d11342567e2771302895e04" commit_message="UPSTREAM: ath10k: wake up offchannel queue properly Once HTT Tx queue got full offchannel queue was stopped and never woken up again. This broke, e.g. P2P. This could be reproduced after running a lot of traffic enough to saturate 100% of the driver Tx queue and then trying to send offchannel traffic. Fixes: 96d828d45e16 ("ath10k: rework tx queue locking") Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 3a73d1a6f22bf13044056543ad43b2a304ee0022) TEST=none BUG=none Change-Id: I97d68782d7362d94d41b28561a156b0ac30c34b1 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307352 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="0" gerrit_number="307352" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/52/307352/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I10d13918247ceb56c2c27c780c8c57e7491ce3f4" commit="1ce4da891692f7f78228ea5ee025cf891efb58f9" commit_message="UPSTREAM: ath10k: wake up queue upon vif creation Vif's vdev_id is used as queue number. However due to the tx pausing design in ath10k it was possible for a new interface to be created with its tx queue stopped (via ieee80211_stop_queues). This could in turn leave the interface inoperable until ath10k_mac_tx_unlock() was called. This problem only affected multi-vif scenarios when new interfaces were created some time later after other interfaces have been running for some time and had Tx queue full at some point prior. Possible manifestation of the bug was authentication timeout for a client vif. Fixes: 96d828d45e16 ("ath10k: rework tx queue locking") Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 6d2d51ecfff13f5f6ffc476dccf4d5b2668072eb) TEST=none BUG=none Change-Id: I10d13918247ceb56c2c27c780c8c57e7491ce3f4 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307353 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="0" gerrit_number="307353" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/53/307353/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="Ib9af0775d67cf4445bc53548c48a25ff90fa5fa6" commit="1afd54f0a74c68ab0ae27000667422798dbcdc10" commit_message="UPSTREAM: ath10k: fix invalid survey reporting for QCA99X0 There are three WMI_CHAN_INFO events reported per channel in QCA99X0 firmware. First one is a notification at the begining of the channel dwell time with cmd_flag as CHAN_INFO_START(cmd_flag = 0), second one is a notification at the end of the dwell time with cmd_flag CHAN_INFO_PRE_COMPLETE (cmd_flag = 2) and the third is the indication with CHAN_INFO_COMPLETE (cmd_flag = 1) which is the last indication for the channel. Since there is a new state before the completion, the handler is to fixed so that the counts are deducted from the ones reported with CHAN_INFO_START rather than the ones reported with CHAN_INFO_PRE_COMPLETE. Without this fix there will be lots of 0 msecs reported as active and busy time. Signed-off-by: Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 3d2a2e293e9578f59b182c8e5ad7b54ec4e28318) TEST=none BUG=none Change-Id: Ib9af0775d67cf4445bc53548c48a25ff90fa5fa6 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307354 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="0" gerrit_number="307354" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/54/307354/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="Ia2aa501c633a026a646b74ba23090f72cf1c09c7" commit="a4f21dd2965073e696813694e522a908ac01f996" commit_message="UPSTREAM: ath10k: add cycle/rx_clear counters frequency to hw_params The frequency at which cycle/rx_clear counters are running might change from one target type to another. QCA99X0 is running the counters at 150Mhz while QCA9888X and QCA6174 are running at 88Mhz. Add a new entry to hw_params to store the target specific frequency and use it in msecs conversion. This change fixes inconsistent channel active/busy time. Signed-off-by: Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 9c8fb548fb242b462657151eb9c5dd6b6def5b62) TEST=none BUG=none Change-Id: Ia2aa501c633a026a646b74ba23090f72cf1c09c7 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307355 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="0" gerrit_number="307355" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/55/307355/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I89f19516b9e276b7727fdd716021949e7c66162a" commit="5d3c60fff575eec348cd7accbb4e76dad39a0fe5" commit_message="UPSTREAM: ath10k: split ap/ibss wep key install process Apparently it's not safe to install both pairwise and groupwise keys on AP vdevs as it can cause traffic to stop working in some multi-vif (WPA+WEP) cases. Fixes: ce90b27128c2 ("ath10k: fix multiple key static wep with ibss") Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 8674d909fabf49140e266f124af68daa3ac93ab3) TEST=none BUG=none Change-Id: I89f19516b9e276b7727fdd716021949e7c66162a Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307356 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="0" gerrit_number="307356" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/56/307356/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I72034595da627fe4dbe48809a7037f8ab2d6de8c" commit="88a0d44e07c1511854ac35ac6c03bb76485215b3" commit_message="UPSTREAM: ath10k: refactor phyerr event handlers Existing phyerr event handlers directly uses phyerr header format (ie, struct wmi_phyerr and struct wmi_phyerr_event) in the code exactly on how firmware packs it. This is the problem in 10.4 fw specific phyerr event handling where it uses different phyerror header format. Before adding 10.4 specific handler, little bit of refactor is done in existing phyerr handlers. Two new abstracted structures (struct wmi_phyerr_ev_hdr_arg and struct wmi_phyerr_ev_arg) are introduced to remove dependency of using firmware specific header format in the code. So that firmware specific phyerror handlers can populate values to abstracted structures and the following code can use abstracted struct for further operation. .pull_phyerr_hdr is added newly to pull common phyerr header info like tsf, buf_len, number of phyerr packed. Existing .pull_phyerr handler is changed and called to parse every sub phyerrs in the event. Validated these refactoring on qca988x hw2.0 using fw 10.2.4 version. Signed-off-by: Raja Mani <rmani@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 991adf71a6cd993c3e6a1a0d8ea9f88b2fa51b95) TEST=none BUG=none Change-Id: I72034595da627fe4dbe48809a7037f8ab2d6de8c Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307357 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="0" gerrit_number="307357" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/57/307357/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="If5e9163eafe75af44baa9bff9e9d45156a72166f" commit="df5ef5adce24648add03c77b309c66f7b956577a" commit_message="UPSTREAM: ath10k: handle 10.4 firmware phyerr event Header format of 10.4 firmware phyerr event is not alligned with pre 10.4 firmware. Introduce new wmi handlers to parse 10.4 firmware specific phyerror event header. With changes covered in this patch, radar detection works on qca9x0 hw 2.0 which uses 10.4 firmware. Signed-off-by: Raja Mani <rmani@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 2b0a2e0d7c2f12d06575fdc2a0f5cc04b131202d) TEST=none BUG=none Change-Id: If5e9163eafe75af44baa9bff9e9d45156a72166f Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307358 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="0" gerrit_number="307358" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/58/307358/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I028329ecc99afdad8e79c3110c3c34414d8bfb8c" commit="5b6688933ab478555295e7bc25b74ab0c3ad0d91" commit_message="UPSTREAM: ath10k: fill in wmi 10.4 command handlers for addba/delba debug commands WMI 10.4 uses the same command interface as QCA988X for addba/delba debug wmi commands. Fill wmi_10_4_ops table with the functions used for QCA988X for these commands. With this change, the following debugfs entries can be used to configure the aggregation mode and to send addba request, addba response and delba respectively in manual aggregation mode for QCA99X0 chip. /sys/kernel/debug/ieee80211/phyX/netdev:wlanX/stations/XX:XX:XX:XX:XX:XX/aggr_mode /sys/kernel/debug/ieee80211/phyX/netdev:wlanX/stations/XX:XX:XX:XX:XX:XX/addba /sys/kernel/debug/ieee80211/phyX/netdev:wlanX/stations/XX:XX:XX:XX:XX:XX/addba_resp /sys/kernel/debug/ieee80211/phyX/netdev:wlanX/stations/XX:XX:XX:XX:XX:XX/delba Signed-off-by: Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit b2887410f0d00f376b250f78d34654b4ac093900) TEST=none BUG=none Change-Id: I028329ecc99afdad8e79c3110c3c34414d8bfb8c Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307359 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="0" gerrit_number="307359" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/59/307359/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="Ief265d4e30b9e98bc538d16d4efd8a69c7dfd9fe" commit="55d0c228b78cab4532a0ab73b88e311b511873a8" commit_message="UPSTREAM: ath10k: ensure pktlog disable cmd reaches fw before pdev suspend Found incorrect sequence in ath10k_core_stop() where wmi pktlog disable cmd is passed from ath10k_debug_stop() to firmware immediately after wmi pdev suspend cmd. Firmware will not accept any wmi cmd after receiving wmi pdev suspend cmd. Fix this issue in ath10k_core_stop() by moving ath10k_debug_stop() just before sending pdev suspend cmd. So that pktlog disable cmd will get passed before pdev suspend cmd. Signed-off-by: Raja Mani <rmani@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit f1ee2682ef8dffe6d6ec6f7788d6bf33d6bab7a6) TEST=none BUG=none Change-Id: Ief265d4e30b9e98bc538d16d4efd8a69c7dfd9fe Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307360 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="0" gerrit_number="307360" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/60/307360/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="Ib726ee0546eb2f42ff817cb808c78b5de16299be" commit="031a92d33594274847b3cdc81054d88e0e6d6b86" commit_message="UPSTREAM: ath10k: free collected fw stats memory if .pull_fw_stats fails If .pull_fw_stats() fails for some reason while processing fw stats event, collected pdev/vdev/peer stats just before the failure should be freed. This is unlikely to happen, just code review catch. Signed-off-by: Raja Mani <rmani@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 5db879aefa0ef6dea4fdda268dd94016bc165f3d) TEST=none BUG=none Change-Id: Ib726ee0546eb2f42ff817cb808c78b5de16299be Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307361 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="0" gerrit_number="307361" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/61/307361/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="Ib475ead0f16f37e3f4c3418642e2802d5afdea02" commit="ddfef95bee5f1df62512f731ebca381243e0b7ef" commit_message="UPSTREAM: ath10k: add missing mutex unlock on failpath Kernel would complain about leaving a held lock after going back to userspace and would subsequently deadlock. Fixes: e04cafbc38c7 ("ath10k: fix peer limit enforcement") Reported-by: Dan Carpenter <dan.carpenter@oracle.com> Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 503422d95248c1d9698735bb5803b70aa51b18ef) TEST=none BUG=none Change-Id: Ib475ead0f16f37e3f4c3418642e2802d5afdea02 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307362 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="0" gerrit_number="307362" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/62/307362/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="Ic85fa48a3063905d611bd5022cbc678646436469" commit="1f8b52e0fe8acecb8582b089d22c29addc6946c9" commit_message="UPSTREAM: ath10k: fix dma_mapping_error() handling The function returns 1 when DMA mapping fails. The driver would return bogus values and could possibly confuse itself if DMA failed. Fixes: 767d34fc67af ("ath10k: remove DMA mapping wrappers") Reported-by: Dan Carpenter <dan.carpenter@oracle.com> Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 5e55e3cbd1042cffa6249f22c10585e63f8a29bf) TEST=none BUG=none Change-Id: Ic85fa48a3063905d611bd5022cbc678646436469 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307363 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="0" gerrit_number="307363" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/63/307363/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="Ie429342df14bc37330f02d5fc84148b600a39fb9" commit="11f045f85a7eb27a199351217c5f420127c966fc" commit_message="UPSTREAM: ath10k: add spectral scan support for 10.4 fw To enable/configure spectral scan parameters in 10.4 firmware, existing wmi spectral related functions can be reused. Link those functions in 10.4 wmi ops table. In addition, adjust bin size (only when size is 68 bytes) before reporting bin samples to user space. The background for this adjustment is that qca99x0 reports bin size as 68 bytes (64 bytes + 4 bytes) in report mode 2. First 64 bytes carries in-band tones (-32 to +31) and last 4 byte carries band edge detection data (+32) mainly used in radar detection purpose. Additional last 4 bytes are stripped to make bin size valid one. This bin size adjustment will happen only for qca99x0, all other chipsets will report proper bin sizes (64/128) without extra 4 bytes being added at the end. The changes are validated in qca99x0 using 10.4 firmware. Signed-off-by: Raja Mani <rmani@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 4535edbd4214ce21328655434c0b75da404e29b7) TEST=none BUG=none Change-Id: Ie429342df14bc37330f02d5fc84148b600a39fb9 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307364 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="0" gerrit_number="307364" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/64/307364/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I35b5256d5df6031c943c645d52d43a45edcf3196" commit="4910a41193052fdc265a88a748678ecad09865eb" commit_message="UPSTREAM: ath10k: add qca6164 support This adds additional 0x0041 PCI Device ID definition to ath10k for QCA6164 which is a 1 spatial stream sibling of the QCA6174 (which is 2 spatial stream chip). The QCA6164 needs a dedicated board.bin file which is different than the one used for QCA6174. If the board.bin is wrong the device will crash early while trying to boot firmware. The register dump will look like this: ath10k_pci 0000:02:00.0: firmware register dump: ath10k_pci 0000:02:00.0: [00]: 0x05010000 0x000015B3 0x000A012D 0x00955B31 ... Note the value 0x000A012D. Special credit goes to Alan Liu <alanliu@qca.qualcomm.com> for providing support help which enabled me to come up with this patch. Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 36582e5d4daeccf68a8a3cef9bc37b60fb7d45b9) TEST=none BUG=none Change-Id: I35b5256d5df6031c943c645d52d43a45edcf3196 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307365 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="0" gerrit_number="307365" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/65/307365/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I6e375a04e870b269be1c427a95d7386457205f9c" commit="fa2d0c042ccefb4e078f9233c23c8e5d7fceb9e3" commit_message="UPSTREAM: ath10k: fix compilation warnings in wmi phyerr pull function Below compilation warnings are observed in gcc version 4.8.2. Even though it's not seen in bit older gcc versions (for ex, 4.7.3), It's good to fix it by changing format specifier from %d to %zd in wmi pull phyerr functions. wmi.c: In function 'ath10k_wmi_op_pull_phyerr_ev': wmi.c:3567:8: warning: format '%d' expects argument of type 'int', but argument 4 has type 'long unsigned int' [-Wformat=] left_len, sizeof(*phyerr)); ^ wmi.c: In function 'ath10k_wmi_10_4_op_pull_phyerr_ev': wmi.c:3612:8: warning: format '%d' expects argument of type 'int', but argument 4 has type 'long unsigned int' [-Wformat=] left_len, sizeof(*phyerr)); ^ Fixes: 991adf71a6cd ("ath10k: refactor phyerr event handlers") Fixes: 2b0a2e0d7c2f ("ath10k: handle 10.4 firmware phyerr event") Signed-off-by: Raja Mani <rmani@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit ee92a2099f79d47e1d6d4857ab308f5b15a00549) TEST=none BUG=none Change-Id: I6e375a04e870b269be1c427a95d7386457205f9c Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307366 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="0" gerrit_number="307366" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/66/307366/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="Icd19ef8561bcc7273f2806b7718c16c7af6de653" commit="9a5b14f3fef1918c5d714ede93da0970a613c961" commit_message="UPSTREAM: ath10k: fix mu-mimo rx status reporting MU-MIMO Rx involves different interpretation of the VHT-SIG-A compared to SU-MIMO. The incorrect interpretation led ath10k to report VHT MCS values greater than 9 which subsequently prompted mac80211 to drop such frames. This effectively broke Rx with MU-MIMO in many cases and manifested with a kernel warning in the log which looked like this: [ 14.552520] WARNING: CPU: 2 PID: 0 at net/mac80211/rx.c:3578 ieee80211_rx+0x26c/0x940 [mac80211]() [ 14.552522] Rate marked as a VHT rate but data is invalid: MCS: 10, NSS: 2 ... call trace follows ... Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 6986fdd699f9be57cc1478c738ea6347e3d52547) TEST=none BUG=none Change-Id: Icd19ef8561bcc7273f2806b7718c16c7af6de653 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307367 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="0" gerrit_number="307367" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/67/307367/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="If2b00b2f6a82f0a7fdcde300b18c59e537b85571" commit="86ae1911b0fea7c21f3ef1f2c1df82efec1d317a" commit_message="UPSTREAM: ath10k: fix DMA alloc failure for target requested memory chunks During long hours of stress testing like AP interface up/down along with continuous ping flood from a station doing connect/disconnect, it is observed that the system is not able to allocate DMA consistent memory of size > 512KB chunks as requested by firmware in WMI_SERVICE_EVENTID. With the system memory getting fragmented during the run based on the size of the memory requested, the failure to return physically continguous memory of high order can happen. Once the system gets to this situation, bringing up the wifi interface will fail and a system reboot may be needed to make it work again. This problem is obseved with QCA99X0. To fix this issue, allocate the DMA memory requested by firmware during device probe time and keep it during the life time of the device. WMI service ready event handler is changed to allocate the memory chunks if it is not already allocated or if the memory allocated for the previous ready event is not same as the current requested ones. After this patch the memory usage when wifi is inactive will be inceased by few 100KB to 3MB based on the target type. Failure happens with the following stack trace [29557.488773] kworker/u4:1: page allocation failure: order:8, mode:0xd0 [29557.494297] CPU: 0 PID: 8402 Comm: kworker/u4:1 Not tainted 3.14.43 #7 [29557.500793] Workqueue: ath10k_aux_wq ath10k_wmi_event_service_ready_work [ath10k_core] [29557.508602] [<c021e9b0>] (unwind_backtrace) from [<c021ba90>] (show_stack+0x10/0x14) [29557.516580] [<c021ba90>] (show_stack) from [<c03bdddc>] (dump_stack+0x88/0xcc) [29557.523612] [<c03bdddc>] (dump_stack) from [<c0290e34>] (warn_alloc_failed+0xdc/0x108) [29557.531515] [<c0290e34>] (warn_alloc_failed) from [<c0292d88>] (__alloc_pages_nodemask+0x4f0/0x654) [29557.540485] [<c0292d88>] (__alloc_pages_nodemask) from [<c0222b48>] (__dma_alloc_buffer.isra.20+0x2c/0x104) [29557.550260] [<c0222b48>] (__dma_alloc_buffer.isra.20) from [<c0222c34>] (__alloc_remap_buffer.isra.23+0x14/0xb8) [29557.560413] [<c0222c34>] (__alloc_remap_buffer.isra.23) from [<c022305c>] (__dma_alloc+0x224/0x2b8) [29557.569490] [<c022305c>] (__dma_alloc) from [<c0223208>] (arm_dma_alloc+0x84/0x90) [29557.577010] [<c0223208>] (arm_dma_alloc) from [<bf5159d0>] (ath10k_wmi_event_service_ready_work+0x2f8/0x420 [ath10k_core]) [29557.588055] [<bf5159d0>] (ath10k_wmi_event_service_ready_work [ath10k_core]) from [<c024260c>] (process_one_work+0x20c/0x328) [29557.599305] [<c024260c>] (process_one_work) from [<c02432d0>] (worker_thread+0x228/0x360) [29557.607470] [<c02432d0>] (worker_thread) from [<c0247f88>] (kthread+0xd8/0xec) [29557.614750] [<c0247f88>] (kthread) from [<c0208d18>] (ret_from_fork+0x14/0x3c) [29557.712751] Normal: 696*4kB (UEMR) 512*8kB (UEMR) 367*16kB (UEMR) 404*32kB (UEMR) 455*64kB (UEMR) 424*128kB (UEMR) 379*256kB (UMR) 327*512kB (UMR) 1*1024kB (R) 0*2048kB 0*4096kB = 374544kB Signed-off-by: Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit a925a3763982799460b9e9b5299520172652b785) TEST=none BUG=none Change-Id: If2b00b2f6a82f0a7fdcde300b18c59e537b85571 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307368 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="0" gerrit_number="307368" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/68/307368/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I9f73923c64a2b820ca5da80dfe93cc3adbb5c6ef" commit="10a79f7a233f3d8f975d532e5aa74c9f42edaae1" commit_message="UPSTREAM: ath10k: drop probe responses when too many are queued In a noisy environment, when multiple interfaces are created, the management tx descriptors are fully occupied by the probe responses from all the interfaces. This prevents a new station from a successful association. Fix this by limiting the probe responses when the specified threshold limit is reached. Signed-off-by: Vivek Natarajan <nataraja@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 7b7da0a02192fd518c26c46dad6b14aca4569605) TEST=none BUG=none Change-Id: I9f73923c64a2b820ca5da80dfe93cc3adbb5c6ef Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307369 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="0" gerrit_number="307369" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/69/307369/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I42b2207766f39e05f72c03284ad1f447aba16c97" commit="0876098b8ca68fb62757a056060188995dd0983f" commit_message="UPSTREAM: ath10k: fix beamformee VHT STS capability The VHT STS CAP shall be reported by firmware to host, like in case of QCA99x0. For QCA6174 hw family this isn't set for some reason. So for this particular chips, let's assume it has the ability to support VHT NDP in up to 4 STSs (which is true by the way). Change the published beamformee STS cap accordingly to 3 or to what the firmware reports. Assumption so far, it suppose to be the num_rf_chains-1, was completely wrong. Signed-off-by: Bartosz Markowski <bartosz.markowski@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 707a0c811ca02861f1500f0696efebcf3bd2e2e2) TEST=none BUG=none Change-Id: I42b2207766f39e05f72c03284ad1f447aba16c97 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307370 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="0" gerrit_number="307370" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/70/307370/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="Iafc6f469026f2f742345f9b59c504b8f631eba19" commit="aa307af4403aef28eb5a7a79f27f34530c6127b4" commit_message="UPSTREAM: ath10k: fix beamformer VHT sounding dimensions capability Similarly to the VHT STS, this is supposed to be propagated by firmware. In case it's not, use the default value, but as last resort. Signed-off-by: Bartosz Markowski <bartosz.markowski@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 0c6d6f2606dfe3758265fb29bfe8103e89d99bab) TEST=none BUG=none Change-Id: Iafc6f469026f2f742345f9b59c504b8f631eba19 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307371 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="0" gerrit_number="307371" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/71/307371/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I50e87b255e9430457de59ad423741d833d25276d" commit="a2dd9b4174f3690e0f9f0490b7c29e825c63f65e" commit_message="UPSTREAM: ath10k: print invalid mcs reported in rx descriptor Sometimes hardware reports invalid mcs index in rx descriptor when operating in VHT80 mode and all packets with invalid mcs will be eventually dropped in mac80211. This issue is observerd during testing on QCA99X0 chipsets. This patch adds a warn message for dumping the rx desc info which helps in analysing the issue when invalid mcs is received. Signed-off-by: Manikanta Pubbisetty <c_mpubbi@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit 6ccea107eba46fbc7de40e944bf17145c2809666) TEST=none BUG=none Change-Id: I50e87b255e9430457de59ad423741d833d25276d Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307372 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="0" gerrit_number="307372" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/72/307372/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.14" change_id="I4524a39619430f3306df67f572b8d1ea23d87976" commit="ab3cd989da6f5e24ee20a56ec75bf6ffc962448e" commit_message="UPSTREAM: ath: DFS - limit number of potential PRI sequences In the PRI detector, after the current radar pulse has been checked agains existing PRI sequences, it is considered as part of a new potential sequence. Previously, the condition to accept a new sequence was to have at least the same number of pulses as the longest matching sequence. This was wrong, since it led to duplicates of PRI sequences. This patch changes the acceptance criteria for new potential sequences from 'at least' to 'more than' the longest existing. Detection performance remains unaffected, while the number of PRI sequences accounted at runtime (and with it CPU load) is reduced by up to 50%. Signed-off-by: Zefir Kurtisi <zefir.kurtisi@neratec.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit b24fc6fc7c0f6425793fd46ccc4ea48f49447617) TEST=none BUG=none Change-Id: I4524a39619430f3306df67f572b8d1ea23d87976 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307014 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307014" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/14/307014/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I94d1ab0e16bad64d97b6556a8e401c1e215c905b" commit="20d30df702861f99614b5438f2483dcd41d2acaa" commit_message="ath6kl: spell "distribution" correctly in a comment. This fixes two misspellings of "distribution" in a comment. Signed-off-by: Nik Nyby <nikolas@gnu.org> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> (cherry picked from commit a0d61f5f61290ee70cd024c7573e2ac5562f7a78) TEST=none BUG=none Change-Id: I94d1ab0e16bad64d97b6556a8e401c1e215c905b Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307015 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307015" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/15/307015/2" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I54b5516101b290398af1e05d0393f92982f01382" commit="f8260b2e809c27f63c7753ec2bc651a5d25ac5d2" commit_message="UPSTREAM: ath: Make ath_opmode_to_string understand OCB mode Make ath_opmode_to_string return "OCB" for NL80211_IFTYPE_OCB. Currently it will return "UNKNOWN". Signed-off-by: Bertold Van den Bergh <bertold.vandenbergh@esat.kuleuven.be> Signed-off-by: Kalle Valo <kvalo@codeaurora.org> (cherry picked from commit 9b412590faaea65dab54f9bc5ae5b48ba0e73c5d) TEST=none BUG=none Change-Id: I54b5516101b290398af1e05d0393f92982f01382 Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/307016 Commit-Ready: Srinivasa duvvuri <sduvvuri@chromium.org> Tested-by: Srinivasa duvvuri <sduvvuri@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@chromium.org> " fail_count="1" gerrit_number="307016" owner_email="akolli@qti.qualcomm.com" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/16/307016/2" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="Ib470266a82395ab73db11e05890d8ab264eda8e4" commit="60478d15884f8064be5e305848754f16dc1374e5" commit_message="Move libmnl to chromiumos-overlay and fix clang build error. The source code in libmnl tries to change the visibility of functions after they have been defined. GCC allows this, but clang does not. The result is that, when built with clang, most functions are 'hidden' and get stripped out altogether. Then anything that tries to use these library functions fails to build. This CL creates a version of the package in chromiumos-overlay (it was in portage stable) and applies an epatch that fixes the source problems for now. The libmnl-function-attributes.patch below was also submitted to the netfilter-devel list, in an attempt to get the patch taken/reviewed upstream: http://marc.info/?l=netfilter-devel&m=144606523930462&w=2 BUG=chromium:548786 TEST=Successfully emerged net-libs/libmnl and sys-apps/iproute2 with clang, with these changes. Change-Id: Ib470266a82395ab73db11e05890d8ab264eda8e4 Reviewed-on: https://chromium-review.googlesource.com/309605 Commit-Ready: Caroline Tice <cmtice@chromium.org> Tested-by: Caroline Tice <cmtice@chromium.org> Reviewed-by: Mike Frysinger <vapier@chromium.org> " fail_count="2" gerrit_number="309605" owner_email="cmtice@chromium.org" pass_count="0" patch_number="4" project="chromiumos/overlays/chromiumos-overlay" project_url="https://chromium-review.googlesource.com/chromiumos/overlays/chromiumos-overlay" ref="refs/changes/05/309605/4" remote="cros" total_fail_count="2"/><pending_commit branch="master" change_id="I36e28e11584cba8c691d0587f29d9d906cb36361" commit="64685ea1dff928a28e0f9d5f0dad995ab59c1024" commit_message="Revert "Temporarily remove smaug from list of important builders in CQ." This reverts commit e6c578e5c00a4bff28999370af0ce3eef4b417e8. smaug-paladin is green again. Thus, reverting this commit. Change-Id: I36e28e11584cba8c691d0587f29d9d906cb36361 Reviewed-on: https://chromium-review.googlesource.com/309897 Commit-Ready: Furquan Shaikh <furquan@chromium.org> Tested-by: Furquan Shaikh <furquan@chromium.org> Reviewed-by: Luigi Semenzato <semenzato@chromium.org> " fail_count="0" gerrit_number="309897" owner_email="furquan@chromium.org" pass_count="0" patch_number="1" project="chromiumos/chromite" project_url="https://chromium-review.googlesource.com/chromiumos/chromite" ref="refs/changes/97/309897/1" remote="cros" total_fail_count="0"/><lkgm version="7597.0.0-rc1"/></manifest> |
