From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: "Kedar J. Karanje" <kedar.j.karanje@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: "Sundaresan, Sujaritha" <sujaritha.sundaresan@intel.com>
Subject: Re: GuC based SLPC
Date: Thu, 24 Jan 2019 07:57:30 +0000 [thread overview]
Message-ID: <77a6ca60-392a-0496-5972-e66d4b313c13@linux.intel.com> (raw)
In-Reply-To: <dcd73252-8df4-b555-c9b7-6424ad5f3074@intel.com>
On 24/01/2019 05:07, Kedar J. Karanje wrote:
> Hello All,
>
> Could some one please let me know who can we contact for the below patch
> series
>
> https://patchwork.freedesktop.org/series/2691/
>
> https://patchwork.freedesktop.org/series/11356/
>
> The mail-ids mentioned in patchwork are failing.
Maybe Sujaritha, based on the latest round of MSRs.
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2019-01-24 7:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 5:07 GuC based SLPC Kedar J. Karanje
2019-01-24 7:57 ` Tvrtko Ursulin [this message]
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=77a6ca60-392a-0496-5972-e66d4b313c13@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kedar.j.karanje@intel.com \
--cc=sujaritha.sundaresan@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