From: Iskren Chernev <iskren.chernev@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Rob Clark <robdclark@gmail.com>,
Sean Paul <seanpaul@chromium.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
~postmarketos/upstreaming@lists.sr.ht
Subject: Re: linux-next: Fixes tag needs some work in the drm-msm tree
Date: Sun, 6 Dec 2020 23:05:30 +0200 [thread overview]
Message-ID: <5820a22b-6fce-20ee-2a48-58c2d57b4ac4@gmail.com> (raw)
In-Reply-To: <20201207070517.28951ed0@canb.auug.org.au>
On 12/6/20 10:05 PM, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 9b73bde39cf2 ("drm/msm: Fix use-after-free in msm_gem with carveout")
>
> Fixes tag
>
> Fixes: 4b85f7f5cf7 ("drm/msm: support for an arbitrary number of
address spaces")
>
> has these problem(s):
>
> - SHA1 should be at least 12 digits long
>
> In the furture, this can be avoided 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").
I'm sorry, I copied and truncated the hash by hand. I should have used
git log --pretty=reference
Also scripts/checkpatch.pl didn't notice it. Should I submit v3 of the
patch or it's too late.
Regards,
Iskren
next prev parent reply other threads:[~2020-12-06 21:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-06 20:05 linux-next: Fixes tag needs some work in the drm-msm tree Stephen Rothwell
2020-12-06 21:05 ` Iskren Chernev [this message]
2020-12-06 21:57 ` Stephen Rothwell
2020-12-06 22:00 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2022-05-01 22:42 Stephen Rothwell
2022-05-01 22:39 Stephen Rothwell
2022-05-01 22:35 Stephen Rothwell
2022-03-02 0:43 Stephen Rothwell
2022-03-02 2:32 ` Dmitry Baryshkov
2021-10-04 21:25 Stephen Rothwell
2021-10-04 21:23 Stephen Rothwell
2021-06-17 22:32 Stephen Rothwell
2021-05-25 0:27 Stephen Rothwell
2021-05-08 2:16 Stephen Rothwell
2020-11-04 20:41 Stephen Rothwell
2020-07-30 22:28 Stephen Rothwell
2020-07-16 0:25 Stephen Rothwell
2020-07-14 0:02 Stephen Rothwell
2020-06-12 4:10 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=5820a22b-6fce-20ee-2a48-58c2d57b4ac4@gmail.com \
--to=iskren.chernev@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=seanpaul@chromium.org \
--cc=sfr@canb.auug.org.au \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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