[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190701074437.6455d067@canb.auug.org.au>
Date: Mon, 1 Jul 2019 07:44:37 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Kalle Valo <kvalo@...eaurora.org>,
Wireless <linux-wireless@...r.kernel.org>
Cc: Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Lorenzo Bianconi <lorenzo@...nel.org>,
Felix Fietkau <nbd@....name>,
Ryder Lee <ryder.lee@...iatek.com>
Subject: linux-next: Fixes tag needs some work in the wireless-drivers-next
tree
Hi all,
In commit
d923cf6bc38a ("mt76: mt7615: fix sparse warnings: warning: cast from restricted __le16")
Fixes tag
Fixes: 3ca0a6f6e9df ("mt7615: mcu: use standard signature for mt7615_mcu_msg_send")
has these problem(s):
- Target SHA1 does not exist
Did you mean
Fixes: 516c3e380533 ("mt7615: mcu: use standard signature for mt7615_mcu_msg_send")
In commit
eda96044de27 ("mt76: mt7615: fix sparse warnings: incorrect type in assignment (different base types)")
Fixes tag
Fixes: 7339fbc0caa5 ("mt7615: mcu: do not use function pointers whenever possible")
has these problem(s):
- Target SHA1 does not exist
Did you mean
Fixes: 1ca8089a55ee ("mt7615: mcu: do not use function pointers whenever possible")
In commit
1a09d9e0e5f0 ("mt76: mt7615: fix incorrect settings in mesh mode")
Fixes tag
Fixes: f072c7ba2150 ("mt76: mt7615: enable support for mesh")
has these problem(s):
- Target SHA1 does not exist
Did you mean
Fixes: f4ec7fdf7f83 ("mt76: mt7615: enable support for mesh")
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists