public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Sujaritha <sujaritha.sundaresan@intel.com>
To: Sagar Arun Kamble <sagar.a.kamble@intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v5 0/5] Removing enable_guc_loading module and Decoupling logs and ADS from submission
Date: Wed, 4 Oct 2017 10:24:49 -0700	[thread overview]
Message-ID: <2134c950-0317-684b-78bb-ae61ebac2c67@intel.com> (raw)
In-Reply-To: <fb63c13c-df53-efee-ccbd-e0f0e4e8062a@intel.com>



On 10/04/2017 12:06 AM, Sagar Arun Kamble wrote:
> Hi Sujaritha,
>
> I am Unable to locate single series on patchwork for these changes.
> Please send all patches together in single series with cover letter.
> It will also enable CI BAT/IGT testing for the series.
>
> Thanks
> Sagar

Sorry, I was not aware of this. I will make sure to send the revised patches
in a single series,

Thanks,
Sujaritha
>
> On 10/4/2017 4:24 AM, Sujaritha Sundaresan wrote:
>> The first patch simpily unifies different seq_puts messages found in 
>> debugfs.
>> In earlier verions, Patch 1 and 2 were previuosly in one single 
>> patch. Patch 2 focuses
>> on replacing the enable_guc_loading module. Patch 3 and 4 deal with 
>> decoupling guc logs
>> and ADS from submission. Patch 5 fixes a warning generated as a 
>> result of patch 4.
>>
>> Cc: Anusha Srivatsa <anusha.srivatsa@intel.com>
>> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
>> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
>> Cc: Oscar Mateo <oscar.mateo@intel.com>
>> Cc: Sagar Arun Kamble <sagar.a.kamble@intel.com>
>>
>> Sujaritha Sundaresan (5):
>>    drm/i915/guc : Unifying seq_puts messages
>>    drm/i915/guc : Removing i915_modparams.enable_guc_loading module
>>    drm/i915/guc : Decouple logs and ADS from submission
>>    drm/i915/guc : group initialization of GuC objects
>>    drm/i915/guc : Fixing argument type warning
>>
>>   drivers/gpu/drm/i915/i915_debugfs.c        |  21 +--
>>   drivers/gpu/drm/i915/i915_drv.h            |   9 +-
>>   drivers/gpu/drm/i915/i915_gem_context.c    |   2 +-
>>   drivers/gpu/drm/i915/i915_gem_gtt.c        |   2 +-
>>   drivers/gpu/drm/i915/i915_guc_submission.c | 118 +----------------
>>   drivers/gpu/drm/i915/i915_irq.c            |   2 +-
>>   drivers/gpu/drm/i915/i915_params.c         |   5 -
>>   drivers/gpu/drm/i915/i915_params.h         |   1 -
>>   drivers/gpu/drm/i915/intel_guc_loader.c    |   7 +-
>>   drivers/gpu/drm/i915/intel_guc_log.c       |   6 +-
>>   drivers/gpu/drm/i915/intel_huc.c           |   4 +-
>>   drivers/gpu/drm/i915/intel_uc.c            | 199 
>> +++++++++++++++++++++++------
>>   drivers/gpu/drm/i915/intel_uc.h            |   7 +-
>>   drivers/gpu/drm/i915/intel_uncore.c        |   4 +-
>>   14 files changed, 202 insertions(+), 185 deletions(-)
>>
>

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2017-10-04 17:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-03 22:54 [PATCH v5 0/5] Removing enable_guc_loading module and Decoupling logs and ADS from submission Sujaritha Sundaresan
2017-10-04  7:06 ` Sagar Arun Kamble
2017-10-04 17:24   ` Sujaritha [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=2134c950-0317-684b-78bb-ae61ebac2c67@intel.com \
    --to=sujaritha.sundaresan@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=sagar.a.kamble@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