diff options
| author | Matthias Kaehlcke <mka@chromium.org> | 2019-07-08 14:57:42 -0700 |
|---|---|---|
| committer | Marcel Holtmann <marcel@holtmann.org> | 2019-08-12 18:23:50 +0200 |
| commit | 2fde6afb8c7fce8e679c1072891cd31d54af5b83 (patch) | |
| tree | c45330d0c1a81eb6c655c86cbdd2bfac094d0dd1 /scripts | |
| parent | 4974c839d45e2ac89ce0e82b49d548cc12e02a9c (diff) | |
| download | linux-2fde6afb8c7fce8e679c1072891cd31d54af5b83.tar.bz2 | |
Bluetooth: btqca: Use correct byte format for opcode of injected command
The opcode of the command injected by commit 32646db8cc28 ("Bluetooth:
btqca: inject command complete event during fw download") uses the CPU
byte format, however it should always be little endian. In practice it
shouldn't really matter, since all we need is an opcode != 0, but still
let's do things correctly and keep sparse happy.
Fixes: 32646db8cc28 ("Bluetooth: btqca: inject command complete event during fw download")
Reported-by: kbuild test robot <lkp@intel.com>
Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions