public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Sagar Arun Kamble <sagar.a.kamble@intel.com>,
	Michal Wajdeczko <michal.wajdeczko@intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 3/6] drm/i915/uc: Create intel_uc_init_mmio
Date: Tue, 03 Oct 2017 11:05:11 +0300	[thread overview]
Message-ID: <1507017911.4728.24.camel@linux.intel.com> (raw)
In-Reply-To: <df102121-1377-dad8-0777-9283efad2e0e@intel.com>

On Tue, 2017-10-03 at 11:28 +0530, Sagar Arun Kamble wrote:
> 
> On 10/2/2017 7:31 PM, Michal Wajdeczko wrote:
> > From: Sagar Arun Kamble <sagar.a.kamble@intel.com>
> > 
> > This patch adds new function intel_uc_init_mmio which will initialize
> > MMIO access related variables prior to uc load/init.
> > 
> > v2: Removed unnecessary export of guc_send_init_regs. Created
> > intel_uc_init_mmio that currently wraps guc_init_send_regs. (Michal)
> > 
> > Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
> > Cc: Michał Winiarski <michal.winiarski@intel.com>
> > Signed-off-by: Sagar Arun Kamble <sagar.a.kamble@intel.com>
> > Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> 
> Looks good to me.
> Acked-by: Sagar Arun Kamble <sagar.a.kamble@intel.com>

Acking code written (even partially) by you would not be the thing
to do :)

https://www.kernel.org/doc/html/v4.12/process/submitting-patches.html#when-to-use-acked-by-and-cc

It has your "From:" and S-o-b, so that should be enough, the
chronological order here should be;

From: Sagar

...

v2 (Michal): ...

S-o-b: Sagar
Cc: Michal
Cc: Michał
S-o-b: Michal

This would show that Sagar originally wrote the patch, and Michael has
made further modifications to the original.

Regards, Joonas
-- 
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-10-03  8:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-02 14:01 [PATCH v2 0/6] drm/i915: Guc code reorg Michal Wajdeczko
2017-10-02 14:01 ` [PATCH v2 1/6] drm/i915/uc: Drop unnecessary forward declaration Michal Wajdeczko
2017-10-02 14:01 ` [PATCH v2 2/6] drm/i915/uc: Move uC fw helper code into dedicated files Michal Wajdeczko
2017-10-03  7:48   ` Joonas Lahtinen
2017-10-02 14:01 ` [PATCH v2 3/6] drm/i915/uc: Create intel_uc_init_mmio Michal Wajdeczko
2017-10-03  5:58   ` Sagar Arun Kamble
2017-10-03  8:05     ` Joonas Lahtinen [this message]
2017-10-03  7:57   ` Joonas Lahtinen
2017-10-02 14:01 ` [PATCH v2 4/6] drm/i915/huc: Move HuC declarations into dedicated header Michal Wajdeczko
2017-10-03  8:10   ` Joonas Lahtinen
2017-10-02 14:01 ` [PATCH v2 5/6] drm/i915/guc: Move Guc early init into own function Michal Wajdeczko
2017-10-03  6:26   ` Sagar Arun Kamble
2017-10-02 14:01 ` [PATCH v2 6/6] drm/i915/guc: Move GuC declarations and functions into dedicated files Michal Wajdeczko
2017-10-03  6:35   ` Sagar Arun Kamble
2017-10-03  8:29   ` Joonas Lahtinen
2017-10-02 14:39 ` ✗ Fi.CI.BAT: failure for drm/i915: Guc code reorg Patchwork

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=1507017911.4728.24.camel@linux.intel.com \
    --to=joonas.lahtinen@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=michal.wajdeczko@intel.com \
    --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