From: Stephen Rothwell <sfr@canb.auug.org.au> To: Dave Airlie <airlied@linux.ie>, DRI <dri-devel@lists.freedesktop.org> Cc: Linux Next Mailing List <linux-next@vger.kernel.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Hans de Goede <hdegoede@redhat.com>, Ben Skeggs <bskeggs@redhat.com> Subject: linux-next: Fixes tag needs some work in the drm-fixes tree Date: Thu, 12 Dec 2019 22:52:02 +1100 [thread overview] Message-ID: <20191212225202.04d0d0e7@canb.auug.org.au> (raw) [-- Attachment #1: Type: text/plain, Size: 371 bytes --] Hi all, n commit 64d17f25dcad ("drm/nouveau: Fix drm-core using atomic code-paths on pre-nv50 hardware") Fixes tag Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1706557 has these problem(s): - No SHA1 recognised I haven't seen a Fixes tag with a bug URL before, they usually reference the buggy commit. -- 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@linux.ie>, DRI <dri-devel@lists.freedesktop.org> Cc: Hans de Goede <hdegoede@redhat.com>, Linux Next Mailing List <linux-next@vger.kernel.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Ben Skeggs <bskeggs@redhat.com> Subject: linux-next: Fixes tag needs some work in the drm-fixes tree Date: Thu, 12 Dec 2019 22:52:02 +1100 [thread overview] Message-ID: <20191212225202.04d0d0e7@canb.auug.org.au> (raw) [-- Attachment #1.1: Type: text/plain, Size: 371 bytes --] Hi all, n commit 64d17f25dcad ("drm/nouveau: Fix drm-core using atomic code-paths on pre-nv50 hardware") Fixes tag Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1706557 has these problem(s): - No SHA1 recognised I haven't seen a Fixes tag with a bug URL before, they usually reference the buggy commit. -- Cheers, Stephen Rothwell [-- Attachment #1.2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 488 bytes --] [-- Attachment #2: Type: text/plain, Size: 160 bytes --] _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-12-12 11:52 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-12-12 11:52 Stephen Rothwell [this message] 2019-12-12 11:52 ` linux-next: Fixes tag needs some work in the drm-fixes tree Stephen Rothwell 2019-12-12 12:35 ` Hans de Goede 2019-12-12 12:35 ` Hans de Goede -- strict thread matches above, loose matches on Subject: below -- 2022-10-28 4:35 Stephen Rothwell 2022-10-28 4:35 ` Stephen Rothwell 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-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=20191212225202.04d0d0e7@canb.auug.org.au \ --to=sfr@canb.auug.org.au \ --cc=airlied@linux.ie \ --cc=bskeggs@redhat.com \ --cc=dri-devel@lists.freedesktop.org \ --cc=hdegoede@redhat.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-next@vger.kernel.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.