From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
Sean Paul <seanpaul@chromium.org>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Gabriel Krisman Bertazi <krisman@collabora.co.uk>
Subject: Re: [PULL] drm-misc-fixes
Date: Fri, 26 May 2017 10:40:15 +0300 [thread overview]
Message-ID: <874lw8nk0w.fsf@intel.com> (raw)
In-Reply-To: <CAKMK7uEARxrRpgsN9cp5hShJU93wjHkCKkzjfAN536HSGb_rtw@mail.gmail.com>
On Fri, 26 May 2017, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> On Thu, May 25, 2017 at 7:44 PM, Sean Paul <seanpaul@chromium.org> wrote:
>> The pull is noisy
>> because it includes -rc2.
>
> dim has you covered for this, in case you've rolled forward but Dave
> hasn't yet, you can regenerate against linus upstream branch for a
> cleaner pull (but still warn Dave ofc):
>
> $ dim pull-request drm-misc-next origin/master
FWIW this is what I've always done with drm-intel-fixes.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-05-26 7:40 UTC|newest]
Thread overview: 133+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 17:44 [PULL] drm-misc-fixes Sean Paul
2017-05-26 5:30 ` Lukas Wunner
2017-05-26 5:59 ` Dave Airlie
2017-05-26 6:36 ` Daniel Vetter
2017-05-26 7:40 ` Jani Nikula [this message]
2017-05-26 14:04 ` Sean Paul
2017-05-28 10:08 ` Lukas Wunner
2017-05-29 6:56 ` Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2024-05-02 19:21 Thomas Zimmermann
2024-04-25 10:24 Thomas Zimmermann
2024-04-18 7:22 Thomas Zimmermann
2024-04-11 7:34 Thomas Zimmermann
2024-04-04 10:48 Thomas Zimmermann
2024-03-28 13:44 Thomas Zimmermann
2024-03-07 8:44 Maxime Ripard
2024-02-29 13:37 Maxime Ripard
2024-02-29 13:54 ` Matthew Auld
2024-03-06 14:26 ` Maxime Ripard
2024-02-22 17:48 Maxime Ripard
2024-02-15 8:49 Maxime Ripard
2024-02-15 12:41 ` Geert Uytterhoeven
2024-02-08 12:02 Maxime Ripard
2024-02-01 9:52 Maxime Ripard
2024-01-26 11:44 Maxime Ripard
2024-01-03 10:47 Maarten Lankhorst
2023-12-14 9:34 Maarten Lankhorst
2023-12-07 12:43 Maarten Lankhorst
2019-11-25 9:43 Maxime Ripard
2019-11-13 14:26 Maxime Ripard
2019-11-07 8:22 Maxime Ripard
2019-10-30 18:22 Maxime Ripard
2019-10-23 11:26 Maxime Ripard
2019-10-17 20:34 Sean Paul
2019-10-10 10:51 Maxime Ripard
2019-10-03 8:10 Maxime Ripard
2019-10-02 20:06 Maxime Ripard
2019-10-03 7:26 ` Maxime Ripard
2019-10-07 14:24 ` Daniel Vetter
2019-09-12 7:13 Maarten Lankhorst
2019-09-05 16:41 Maarten Lankhorst
2019-08-28 18:57 Maarten Lankhorst
2019-08-22 10:22 Maarten Lankhorst
2019-08-08 9:01 Maarten Lankhorst
2019-08-02 13:43 Maarten Lankhorst
2019-08-02 15:07 ` Daniel Vetter
2019-07-25 16:09 Sean Paul
2019-07-04 0:13 Sean Paul
2019-06-26 20:56 Sean Paul
2019-06-19 19:27 Sean Paul
2019-06-13 14:39 Sean Paul
2019-06-13 20:45 ` Daniel Vetter
2019-06-05 21:03 Sean Paul
2019-05-29 21:18 Sean Paul
2019-05-22 19:44 Sean Paul
2019-05-02 12:25 Maxime Ripard
2019-04-25 13:27 Maxime Ripard
2019-04-11 15:16 Maxime Ripard
2019-03-25 10:45 Maxime Ripard
2019-02-22 8:57 Maarten Lankhorst
2019-02-13 10:01 Maarten Lankhorst via dri-devel
2019-02-07 8:21 Maarten Lankhorst
2019-01-24 8:25 Maarten Lankhorst
2019-01-17 11:06 Maarten Lankhorst
2019-01-10 6:52 Maarten Lankhorst
2018-12-20 16:57 Sean Paul
2018-12-20 17:32 ` Daniel Vetter
2018-12-12 20:43 Sean Paul
2018-12-05 20:14 Sean Paul
2018-11-28 20:04 Sean Paul
2018-11-28 20:36 ` Sean Paul
2018-11-21 15:52 Sean Paul
2018-11-14 20:45 Sean Paul
2018-11-07 20:50 Sean Paul
2018-10-19 10:57 Maarten Lankhorst
2018-10-18 16:28 Maarten Lankhorst
2018-10-04 8:37 Maarten Lankhorst
2018-09-27 15:27 Sean Paul
2018-09-27 10:02 Maarten Lankhorst
2018-09-19 14:32 Maarten Lankhorst
2018-07-27 8:24 Maarten Lankhorst
2018-07-13 7:28 Maarten Lankhorst
2018-07-05 13:19 Maarten Lankhorst
2018-06-28 9:49 Maarten Lankhorst
2018-06-21 14:08 Maarten Lankhorst
2018-06-12 9:09 Maarten Lankhorst
2018-05-16 19:21 Sean Paul
2018-05-09 20:26 Sean Paul
2018-05-02 19:53 Sean Paul
2018-04-25 19:39 Sean Paul
2018-04-18 19:26 Sean Paul
2018-03-22 18:57 Gustavo Padovan
2018-03-07 10:35 Gustavo Padovan
2018-02-28 15:37 Gustavo Padovan
2018-02-21 15:23 Gustavo Padovan
2018-01-31 15:16 Gustavo Padovan
2018-01-31 15:36 ` Gustavo Padovan
2018-01-17 9:26 Daniel Vetter
2018-01-08 9:51 Daniel Vetter
2017-12-21 13:01 Daniel Vetter
2017-12-14 14:50 Daniel Vetter
2017-12-14 19:48 ` Linus Torvalds
2017-12-07 15:04 Daniel Vetter
2017-12-06 21:03 Daniel Vetter
2017-11-30 7:44 Daniel Vetter
2017-11-20 15:27 Daniel Vetter
2017-11-13 19:27 Sean Paul
2017-11-02 13:13 Sean Paul
2017-10-11 19:54 Sean Paul
2017-10-05 11:23 Daniel Vetter
2017-09-28 10:37 Sean Paul
2017-08-28 21:18 Sean Paul
2017-08-24 14:09 Sean Paul
2017-08-18 15:57 Sean Paul
2017-08-18 20:19 ` Daniel Vetter
2017-08-18 20:29 ` Sean Paul
2017-08-09 13:52 Sean Paul
2017-07-27 19:32 Sean Paul
2017-07-20 21:19 Sean Paul
2017-06-15 20:13 Sean Paul
2017-06-08 0:22 Sean Paul
2017-06-02 18:33 Sean Paul
2017-03-31 6:07 Daniel Vetter
2017-03-23 15:50 Daniel Vetter
2017-03-06 9:41 Daniel Vetter
2017-02-09 7:51 Daniel Vetter
2017-01-31 17:11 Daniel Vetter
2017-01-23 10:11 Daniel Vetter
2017-01-13 8:11 Daniel Vetter
2017-01-09 19:17 Daniel Vetter
2017-01-04 16:24 Daniel Vetter
2016-12-22 7:29 Daniel Vetter
2016-11-30 19:29 Daniel Vetter
2016-10-27 6:36 Daniel Vetter
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=874lw8nk0w.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=krisman@collabora.co.uk \
--cc=seanpaul@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: 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).