From: "Heiko Stübner" <heiko@sntech.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Dave Airlie <airlied@linux.ie>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
DRI <dri-devel@lists.freedesktop.org>
Subject: Re: linux-next: Fixes tag needs some work in the drm-fixes tree
Date: Fri, 08 Feb 2019 12:31:38 +0100 [thread overview]
Message-ID: <2145777.rZLEu8YqWI@diego> (raw)
In-Reply-To: <20190208220137.3b72799a@canb.auug.org.au>
Am Freitag, 8. Februar 2019, 12:01:37 CET schrieb Stephen Rothwell:
> Hi all,
>
> In commit
>
> 053ff09f1a8f ("drm/rockchip: rgb: update SPDX license identifier")
>
> Fixes tag
>
> Fixes: 1f0f01515172 ("Add support for Rockchip Soc RGB output interface")
>
> has these problem(s):
>
> - Subject does not match target commit subject
we had this warning already from the drm-misc-fixes tree :-) .
And the drm-* history is very much fixed (due to it being a shared tree)
so we'll probably have to live with that mistake I made (missing the
"drm/rockchip:" prefix from the subject). But as I said the other time,
it should hopefully be still be identifiable.
Heiko
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-02-08 11:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 11:01 linux-next: Fixes tag needs some work in the drm-fixes tree Stephen Rothwell
2019-02-08 11:31 ` Heiko Stübner [this message]
2019-02-08 11:40 ` Stephen Rothwell
2019-02-08 11:45 ` Heiko Stübner
-- 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-12-12 11:52 Stephen Rothwell
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-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=2145777.rZLEu8YqWI@diego \
--to=heiko@sntech.de \
--cc=airlied@linux.ie \
--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).