From: Stephen Rothwell <sfr@canb.auug.org.au> To: Dave Airlie <airlied@redhat.com>, DRI <dri-devel@lists.freedesktop.org> Cc: Akhil P Oommen <quic_akhilpo@quicinc.com>, Rob Clark <robdclark@chromium.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Linux Next Mailing List <linux-next@vger.kernel.org> Subject: linux-next: Fixes tag needs some work in the drm-fixes tree Date: Fri, 28 Oct 2022 15:35:45 +1100 [thread overview] Message-ID: <20221028153545.0a5195a8@canb.auug.org.au> (raw) [-- Attachment #1: Type: text/plain, Size: 441 bytes --] Hi all, In commit ec8f1813bf8d ("drm/msm/a6xx: Replace kcalloc() with kvzalloc()") Fixes tag Fixes: b859f9b009b (drm/msm/gpu: Snapshot GMU debug buffer) has these problem(s): - SHA1 should be at least 12 digits long This can be fixed for the future 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"). -- Cheers, Stephen Rothwell [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Rothwell <sfr@canb.auug.org.au> To: Dave Airlie <airlied@redhat.com>, DRI <dri-devel@lists.freedesktop.org> Cc: Akhil P Oommen <quic_akhilpo@quicinc.com>, Rob Clark <robdclark@chromium.org>, Linux Next Mailing List <linux-next@vger.kernel.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org> Subject: linux-next: Fixes tag needs some work in the drm-fixes tree Date: Fri, 28 Oct 2022 15:35:45 +1100 [thread overview] Message-ID: <20221028153545.0a5195a8@canb.auug.org.au> (raw) [-- Attachment #1: Type: text/plain, Size: 441 bytes --] Hi all, In commit ec8f1813bf8d ("drm/msm/a6xx: Replace kcalloc() with kvzalloc()") Fixes tag Fixes: b859f9b009b (drm/msm/gpu: Snapshot GMU debug buffer) has these problem(s): - SHA1 should be at least 12 digits long This can be fixed for the future 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"). -- Cheers, Stephen Rothwell [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-10-28 4:35 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-28 4:35 Stephen Rothwell [this message] 2022-10-28 4:35 ` linux-next: Fixes tag needs some work in the drm-fixes tree Stephen Rothwell -- strict thread matches above, loose matches on Subject: below -- 2021-10-12 10:36 Stephen Rothwell 2020-10-30 4:42 Stephen Rothwell 2020-10-30 4:42 ` Stephen Rothwell 2020-07-27 13:38 Stephen Rothwell 2020-07-27 13:38 ` Stephen Rothwell 2020-07-28 9:50 ` Daniel Vetter 2020-07-28 9:50 ` Daniel Vetter 2019-12-12 11:52 Stephen Rothwell 2019-12-12 11:52 ` Stephen Rothwell 2019-12-12 12:35 ` Hans de Goede 2019-12-12 12:35 ` Hans de Goede 2019-05-31 6:11 Stephen Rothwell 2019-04-17 21:46 Stephen Rothwell 2019-04-18 7:39 ` Daniel Vetter 2019-02-08 11:01 Stephen Rothwell 2019-02-08 11:31 ` Heiko Stübner 2019-02-08 11:31 ` Heiko Stübner 2019-02-08 11:40 ` Stephen Rothwell 2019-02-08 11:40 ` Stephen Rothwell 2019-02-08 11:45 ` Heiko Stübner 2019-01-18 4:42 Stephen Rothwell 2019-01-18 4:42 ` 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=20221028153545.0a5195a8@canb.auug.org.au \ --to=sfr@canb.auug.org.au \ --cc=airlied@redhat.com \ --cc=dri-devel@lists.freedesktop.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-next@vger.kernel.org \ --cc=quic_akhilpo@quicinc.com \ --cc=robdclark@chromium.org \ /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: linkBe 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.