From: Hans de Goede <hdegoede@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
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>,
Ben Skeggs <bskeggs@redhat.com>
Subject: Re: linux-next: Fixes tag needs some work in the drm-fixes tree
Date: Thu, 12 Dec 2019 13:35:55 +0100 [thread overview]
Message-ID: <2dd7955d-5477-d110-9409-1c42444ac03d@redhat.com> (raw)
In-Reply-To: <20191212225202.04d0d0e7@canb.auug.org.au>
Hi,
On 12-12-2019 12:52, Stephen Rothwell wrote:
> 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.
Sorry my bad, that should have been a BugLink tag. The patch in question is a bugfix,
but it is sorta hard to pinpoint the cause to a specific commit, this problem was
probably introduced during the conversion of nouveau to support atomic modesetting,
which is quite a while ago and involves lots of patches.
Not sure how to best fix this since fixing would require rewriting history. I hope this
is just something we can live with?
Regards,
Hans
next prev parent reply other threads:[~2019-12-12 12:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-28 4:35 Stephen Rothwell
2021-10-12 10:36 Stephen Rothwell
2020-10-30 4:42 Stephen Rothwell
2020-07-27 13:38 Stephen Rothwell
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:40 ` Stephen Rothwell
2019-02-08 11:45 ` Heiko Stübner
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=2dd7955d-5477-d110-9409-1c42444ac03d@redhat.com \
--to=hdegoede@redhat.com \
--cc=airlied@linux.ie \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).