From: "Heiko Stübner" <heiko@sntech.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Dave Airlie <airlied@linux.ie>,
DRI <dri-devel@lists.freedesktop.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Sandy Huang <hjc@rock-chips.com>
Subject: Re: linux-next: Fixes tag needs some work in the drm-fixes tree
Date: Fri, 08 Feb 2019 12:45:47 +0100 [thread overview]
Message-ID: <3023200.v8ugM0oLqk@diego> (raw)
In-Reply-To: <20190208224022.6bfdd56d@canb.auug.org.au>
Am Freitag, 8. Februar 2019, 12:40:22 CET schrieb Stephen Rothwell:
> Hi Heiko,
>
> On Fri, 08 Feb 2019 12:31:38 +0100 Heiko Stübner <heiko@sntech.de> wrote:
> > we had this warning already from the drm-misc-fixes tree :-) .
>
> Sorry about that ... there goes my memory again :-)
No worries :-D ... I don't really expect you to remember
thousands of commits individually :-) .
next prev parent reply other threads:[~2019-02-08 11:45 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
2019-02-08 11:40 ` Stephen Rothwell
2019-02-08 11:45 ` Heiko Stübner [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-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=3023200.v8ugM0oLqk@diego \
--to=heiko@sntech.de \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=hjc@rock-chips.com \
--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).