From: Jani Nikula <jani.nikula@intel.com>
To: "Nagaraju, Vathsala" <vathsala.nagaraju@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: Puthikorn Voravootivat <puthik@chromium.org>,
Maulik V Vaghela <maulik.v.vaghela@intel.com>,
Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH] drm/i915/psr: vbt change for psr
Date: Wed, 23 May 2018 16:10:59 +0300 [thread overview]
Message-ID: <87lgcaldp8.fsf@intel.com> (raw)
In-Reply-To: <e07b3776-5b85-8370-c164-84db89d8fd6d@intel.com>
On Wed, 23 May 2018, "Nagaraju, Vathsala" <vathsala.nagaraju@intel.com> wrote:
> On 5/23/2018 3:33 PM, Jani Nikula wrote:
>> Why did you send this again? Did you change something? I already
>> reviewed the version from yesterday.
> no code change, added only rb tag by you and resent it.
For future reference, you should *not* resend for that.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-05-23 13:07 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 3:05 [PATCH] drm/i915/psr: vbt change for psr vathsala nagaraju
2018-05-23 3:24 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/psr: vbt change for psr (rev10) Patchwork
2018-05-23 3:45 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-05-23 10:03 ` [PATCH] drm/i915/psr: vbt change for psr Jani Nikula
2018-05-23 12:55 ` Nagaraju, Vathsala
2018-05-23 13:10 ` Jani Nikula [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-22 9:27 vathsala nagaraju
2018-05-22 12:46 ` Jani Nikula
2018-05-24 13:04 ` Jani Nikula
2018-05-18 8:55 vathsala nagaraju
2018-05-18 9:31 ` Jani Nikula
2018-05-22 4:48 ` Nagaraju, Vathsala
2018-05-22 8:05 ` Jani Nikula
2018-05-22 8:36 ` Nagaraju, Vathsala
2018-05-14 3:32 vathsala nagaraju
2018-05-15 22:55 ` Puthikorn Voravootivat
2018-05-16 3:48 ` vathsala nagaraju
2018-05-15 23:03 ` Dhinakaran Pandiyan
2018-05-16 3:44 ` vathsala nagaraju
2018-05-16 8:08 ` Jani Nikula
2018-05-16 17:44 ` Dhinakaran Pandiyan
2018-05-17 8:02 ` Jani Nikula
2018-05-17 20:12 ` Dhinakaran Pandiyan
2018-05-16 8:13 ` Jani Nikula
2018-05-16 22:04 ` Dhinakaran Pandiyan
2018-05-03 11:36 vathsala nagaraju
2018-05-03 15:44 ` Rodrigo Vivi
2018-05-03 17:13 ` Nagaraju, Vathsala
2018-05-04 23:13 ` Puthikorn Voravootivat
2018-05-03 9:08 vathsala nagaraju
2018-05-03 9:39 ` Jani Nikula
2018-05-02 9:13 vathsala nagaraju
2018-05-02 21:15 ` Rodrigo Vivi
2018-05-03 3:21 ` vathsala nagaraju
2018-05-03 6:59 ` Jani Nikula
2018-05-03 7:07 ` Jani Nikula
2018-04-19 7:42 vathsala nagaraju
2018-04-19 13:35 ` Jani Nikula
2018-04-20 6:30 ` vathsala nagaraju
2018-04-27 7:52 ` Jani Nikula
2018-04-11 17:57 vathsala nagaraju
2018-04-12 9:26 ` Jani Nikula
2018-04-06 17:28 vathsala nagaraju
2018-04-06 17:41 ` Rodrigo Vivi
2018-04-09 13:57 ` Jani Nikula
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=87lgcaldp8.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=dhinakaran.pandiyan@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maulik.v.vaghela@intel.com \
--cc=puthik@chromium.org \
--cc=rodrigo.vivi@intel.com \
--cc=vathsala.nagaraju@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 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).