From: Mahesh Kumar <mahesh1.kumar@intel.com>
To: Jani Nikula <jani.nikula@intel.com>, intel-gfx@lists.freedesktop.org
Cc: paulo.r.zanoni@intel.com, maarten.lankhorst@intel.com
Subject: Re: [PATCH 0/8] Fixed16.16 wrapper cleanup & wm optimization
Date: Thu, 17 Aug 2017 20:46:16 +0530 [thread overview]
Message-ID: <b86d4c2d-9beb-c16e-e1ca-748bd408f52b@intel.com> (raw)
In-Reply-To: <87h8x68dgn.fsf@nikula.org>
Hi,
My bad, I forgot to modify cover-letter before sending series to intel-gfx.
yes this is for upstream consideration.
-Mahesh
On Thursday 17 August 2017 08:10 PM, Jani Nikula wrote:
> On Thu, 17 Aug 2017, Mahesh Kumar <mahesh1.kumar@intel.com> wrote:
>> This is a Trybot Version of series.
> What do you mean? Is this for upstream consideration or not?
>
> BR,
> Jani.
>
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-08-17 15:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 13:45 [PATCH 0/8] Fixed16.16 wrapper cleanup & wm optimization Mahesh Kumar
2017-08-17 13:45 ` [PATCH 1/8] drm/i915: Fixed point fixed16 wrapper cleanup Mahesh Kumar
2017-08-17 13:45 ` [PATCH 2/8] drm/i915/skl+: Optimize WM calculation Mahesh Kumar
2017-08-17 13:45 ` [PATCH 3/8] drm/i915/gen10: Calculate and enable transition WM Mahesh Kumar
2017-08-17 13:45 ` [PATCH 4/8] drm/i915/glk: IPC linetime watermark workaround for GLK Mahesh Kumar
2017-08-17 13:45 ` [PATCH 5/8] drm/i915/cnl: Extend WM workaround with IPC for CNL Mahesh Kumar
2017-08-17 13:45 ` [PATCH 6/8] drm/i915/gen9+: Add has_ipc flag in device info structure Mahesh Kumar
2017-08-17 13:45 ` [PATCH 7/8] drm/i915/bxt+: Enable IPC support Mahesh Kumar
2017-08-17 13:45 ` [PATCH 8/8] drm/i915/skl+: debugfs entry to control IPC Mahesh Kumar
2017-08-17 14:00 ` ✗ Fi.CI.BAT: warning for Fixed16.16 wrapper cleanup & wm optimization (rev7) Patchwork
2017-08-17 14:40 ` [PATCH 0/8] Fixed16.16 wrapper cleanup & wm optimization Jani Nikula
2017-08-17 15:16 ` Mahesh Kumar [this message]
2017-09-07 15:11 ` Maarten Lankhorst
2017-09-05 9:09 ` ✓ Fi.CI.BAT: success for Fixed16.16 wrapper cleanup & wm optimization (rev7) Patchwork
2017-09-05 10:14 ` ✓ Fi.CI.IGT: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2017-07-18 12:49 [PATCH 0/8] Fixed16.16 wrapper cleanup & wm optimization Mahesh Kumar
2017-06-21 6:14 Mahesh Kumar
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=b86d4c2d-9beb-c16e-e1ca-748bd408f52b@intel.com \
--to=mahesh1.kumar@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=maarten.lankhorst@intel.com \
--cc=paulo.r.zanoni@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.