From: Kalle Valo <kvalo@codeaurora•org>
To: John Crispin <john@phrozen•org>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Wireless <linux-wireless@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Pradeep Kumar Chitrapu <pradeepc@codeaurora•org>
Subject: Re: linux-next: Fixes tag needs some work in the wireless-drivers tree
Date: Fri, 20 Dec 2019 10:48:45 +0200 [thread overview]
Message-ID: <87y2v72xhu.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <739b70e9-6a77-9d4e-2331-16022325cd34@phrozen.org> (John Crispin's message of "Thu, 19 Dec 2019 21:55:32 +0100")
John Crispin <john@phrozen•org> writes:
> On 19/12/2019 21:53, Stephen Rothwell wrote:
>> Hi all,
>>
>> In commit
>>
>> 485add35771b ("ath11k: fix pdev when invoking ath11k_wmi_send_twt_enable_cmd()")
>>
>> Fixes tag
>>
>> Fixes: e65a616f4e74 ("ath11k: add TWT support")
>>
>> has these problem(s):
>>
>> - Target SHA1 does not exist
>>
>> Did you mean
>>
>> Fixes: 6d293d447670 ("ath11k: add TWT support")
>>
>
> My bad, sorry, I was sitting on an old tree apparently.
And I didn't catch it either. I try to avoid rebasing my trees so I'm
not planning fix this, let's just avoid this in the future.
--
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2019-12-20 8:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 20:53 linux-next: Fixes tag needs some work in the wireless-drivers tree Stephen Rothwell
2019-12-19 20:55 ` John Crispin
2019-12-20 8:48 ` Kalle Valo [this message]
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=87y2v72xhu.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora$(echo .)org \
--cc=john@phrozen$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-wireless@vger$(echo .)kernel.org \
--cc=pradeepc@codeaurora$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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