From: Rodrigo Vivi <rodrigo.vivi@gmail.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH 0/6] drm-intel-collector - update
Date: Mon, 7 Apr 2014 16:59:09 -0300 [thread overview]
Message-ID: <1396900755-2391-1-git-send-email-rodrigo.vivi@gmail.com> (raw)
This is another drm-intel-collector updated notice:
http://cgit.freedesktop.org/~vivijim/drm-intel/log/?h=drm-intel-collector
Here goes the update list in order for better reviewers assignment:
Patch drm/i915: Bring UP Power Wells before disabling RC6. - Reviewer:
Patch drm/i915: dma_buf_vunmap is presumed not to fail, don't let it - Reviewer:
Patch drm/i915: Add support for stealing purgable stolen pages - Reviewer:
Patch drm/i915: add flag to prevent dmesg spam on context banning - Reviewer:
Patch drm/i915: Do not allow a pending forcewake put to unbalance across reset - Reviewer:
Patch drm/i915: Don't save/restore RS when not used - Reviewer:
Overall Process:
drm-intel-collector - review request
1. Daniel pushs drm-intel-testing (every 2 weeks)
2. I rebase drm-intel-collector onto drm-intel-testing
3. Add Reviewer: tag with voluntered reviewers. If you don't believe you should be assigned on a particular patch please don't get mad just tell you wont review or volunteer someone else.
4. I resubmit remaining patches for review without picking any new (drm-intel-collector - review request)
drm-intel-collector - updated
5. One week later I collect all simple (1-2) patches that wasn't yet reviewed and not queued by Daniel from one testing update until another.
6. Request automated QA's PRTS automated i-g-t tests comparing drm-intel-testing x drm-intel-collector
7. If tests are ok I send the update notification or the patches as a series to intel-gfx mailing list for better tracking and to be reviewed. (drm-intel-collector - updated)
8. Let me know volunteers for review new patches and also let me know if I've picked any patch that I shouldn't.
There are some reasons that some patches can be left behind:
1. Your patch didn't applied cleanly and I couldn't easily solve the conflicts.
2. Kernel didn't compiled with your patch.
3. I simply missed it. If you believe this is the case please warn me.
Please help me to get these patches reviewed and queued by Daniel.
Also, please let me know if you have further ideas how to improve this process.
Thanks in advance,
Rodrigo.
Ben Widawsky (1):
drm/i915: Don't save/restore RS when not used
Chris Wilson (3):
drm/i915: dma_buf_vunmap is presumed not to fail, don't let it
drm/i915: Add support for stealing purgable stolen pages
drm/i915: Do not allow a pending forcewake put to unbalance across
reset
Deepak S (1):
drm/i915: Bring UP Power Wells before disabling RC6.
Mika Kuoppala (1):
drm/i915: add flag to prevent dmesg spam on context banning
drivers/gpu/drm/i915/i915_drv.h | 18 ++++-
drivers/gpu/drm/i915/i915_gem.c | 5 +-
drivers/gpu/drm/i915/i915_gem_context.c | 12 ++--
drivers/gpu/drm/i915/i915_gem_dmabuf.c | 6 +-
drivers/gpu/drm/i915/i915_gem_stolen.c | 119 +++++++++++++++++++++++++++++---
drivers/gpu/drm/i915/intel_pm.c | 6 ++
drivers/gpu/drm/i915/intel_ringbuffer.c | 2 +-
drivers/gpu/drm/i915/intel_uncore.c | 5 +-
8 files changed, 146 insertions(+), 27 deletions(-)
--
1.9.0
next reply other threads:[~2014-04-07 19:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 19:59 Rodrigo Vivi [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-04-07 20:01 [PATCH 0/6] drm-intel-collector - update Rodrigo Vivi
2013-12-02 13:26 Rodrigo Vivi
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=1396900755-2391-1-git-send-email-rodrigo.vivi@gmail.com \
--to=rodrigo.vivi@gmail.com \
--cc=intel-gfx@lists.freedesktop.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