From: Kalle Valo <kvalo@codeaurora.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Wireless <linux-wireless@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rakesh Pillai <pillair@codeaurora.org>
Subject: Re: linux-next: Fixes tag needs some work in the wireless-drivers-next tree
Date: Wed, 29 Jan 2020 16:05:32 +0200 [thread overview]
Message-ID: <87k15a8ij7.fsf@codeaurora.org> (raw)
In-Reply-To: <20200127114221.52ba6027@canb.auug.org.au> (Stephen Rothwell's message of "Mon, 27 Jan 2020 11:42:21 +1100")
Stephen Rothwell <sfr@canb.auug.org.au> writes:
> Hi all,
>
> n commit
>
> 6ba8b3b6bd77 ("ath10k: Correct the DMA direction for management tx buffers")
>
> Fixes tag
>
> Fixes: dc405152bb6 ("ath10k: handle mgmt tx completion event")
>
> has these problem(s):
>
> - SHA1 should be at least 12 digits long
> Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
> or later) just making sure it is not set (or set to "auto").
Doh, I missed that but naturally there's nothing we can do now as the
commit is in Linus' tree. I really should implement some kind of
automatic check to my patchwork script for this.
--
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2020-01-29 14:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 0:42 linux-next: Fixes tag needs some work in the wireless-drivers-next tree Stephen Rothwell
2020-01-29 14:05 ` Kalle Valo [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
2019-07-01 21:33 Stephen Rothwell
2019-07-02 4:26 ` dundi
2019-06-30 21:44 Stephen Rothwell
2019-07-01 10:35 ` Lorenzo Bianconi
2019-05-27 21:48 Stephen Rothwell
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=87k15a8ij7.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pillair@codeaurora.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.