From: Lorenzo Bianconi <lorenzo@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Kalle Valo <kvalo@codeaurora.org>,
Wireless <linux-wireless@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Felix Fietkau <nbd@nbd.name>, Ryder Lee <ryder.lee@mediatek.com>
Subject: Re: linux-next: Fixes tag needs some work in the wireless-drivers-next tree
Date: Mon, 1 Jul 2019 12:35:20 +0200 [thread overview]
Message-ID: <20190701103520.GB5110@localhost.localdomain> (raw)
In-Reply-To: <20190701074437.6455d067@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1403 bytes --]
> 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")
Hi Stephen,
I used the hashes from my local git tree that are different from upstream ones,
sorry for the inconvenience. I will pay more attention next time.
Regards,
Lorenzo
>
> --
> Cheers,
> Stephen Rothwell
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2019-07-01 10:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-30 21:44 linux-next: Fixes tag needs some work in the wireless-drivers-next tree Stephen Rothwell
2019-07-01 10:35 ` Lorenzo Bianconi [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-08-18 22:33 Stephen Rothwell
2020-08-19 6:52 ` Kalle Valo
2020-08-19 8:13 ` Stephen Rothwell
2020-09-24 16:11 ` Kalle Valo
2020-08-02 22:03 Stephen Rothwell
2020-08-04 13:17 ` Kalle Valo
2020-07-14 10:59 Stephen Rothwell
2020-07-14 17:49 ` Kalle Valo
2020-05-18 13:01 Stephen Rothwell
2020-05-19 8:50 ` Kalle Valo
2020-04-14 22:08 Stephen Rothwell
2020-04-15 0:36 ` Larry Finger
2020-04-15 1:06 ` Stephen Rothwell
2020-04-15 4:45 ` Kalle Valo
2020-01-27 0:42 Stephen Rothwell
2020-01-29 14:05 ` Kalle Valo
2019-07-01 21:33 Stephen Rothwell
2019-07-02 4:26 ` dundi
2019-05-27 21:48 Stephen Rothwell
2019-05-01 21:50 Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190701103520.GB5110@localhost.localdomain \
--to=lorenzo@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=ryder.lee@mediatek.com \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).