All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@gmail.com>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
	Sujaritha Sundaresan <sujaritha.sundaresan@intel.com>
Subject: Re: [PATCH v5 2/5] drm/i915/guc : Removing i915_modparams.enable_guc_loading module
Date: Thu, 2 Nov 2017 16:52:45 -0700	[thread overview]
Message-ID: <CABVU7+vW_E27hA_8H+iWUcs4_ufdUrqsZw_pauQLOPn_87K6xA@mail.gmail.com> (raw)
In-Reply-To: <1507122459.5856.15.camel@linux.intel.com>

On Wed, Oct 4, 2017 at 6:07 AM, Joonas Lahtinen
<joonas.lahtinen@linux.intel.com> wrote:
> On Tue, 2017-10-03 at 15:56 -0700, Sujaritha Sundaresan wrote:
>> We currently have two module parameters that control GuC: "enable_guc_loading" and "enable_guc_submission".
>> Whenever we need i915_modparams.enable_guc_submission=1, we also need enable_guc_loading=1.
>> We also need enable_guc_loading=1 when we want to verify the HuC,
>> which is every time we have a HuC (but all platforms with HuC have a GuC and viceversa).
>
> Long lines in commit message, please give a look at:
>
> https://www.kernel.org/doc/html/v4.13/process/submitting-patches.html
>
> Section "14) The canonical patch format".
>
> Then, about the patch. I think the commit message should be more clear
> about the fact that if we have HuC firmware to be loaded, we need to
> have GuC to actually load it. So if an user wants to avoid the GuC from
> getting loaded, they must not have a HuC firmware to be loaded, in
> addition to not using GuC submission.
>
>>
>> v2: Clarifying the commit message (Anusha)
>>
>> v3: Unify seq_puts messages, Re-factoring code as per review (Michal)
>>
>> v4: Rebase
>>
>> v5: Separating message unification into a separate patch
>>
>> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
>> Cc: Anusha Srivatsa <anusha.srivatsa@intel.com>
>> Cc: Oscar Mateo <oscar.mateo@intel.com>
>> Cc: Sagar Arun Kamble <sagar.a.kamble@intel.com>
>> Signed-off-by: Sujaritha Sundaresan <sujaritha.sundaresan@intel.com>
>
> Try to keep the tags in chronological order, so start with Suggested-
> by: (if any), Signed-off-by:, Cc: and so on.

Could we agree on have
Suggested-by:
Cc:
Signed-off-by:
as the initial chronological order and then follow the chronological
after that as well?

Few reasons for that:
1. For my brain this is the regular chronological message flow:
someone suggested, you message some one and last thing you do before
sending the message is to sign-off.
2. git commit --amend -s adds it to the end.
3. Signed-off-by: at the end of the message was always our standard
and every patch that I see around in the kernel seems to prefer this
style
4. When I look to the first email and I see cc below the first thing
that I think is: "This developer forgot to sign-off his own patch!".

Thanks,
Rodrigo.

>
> 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



-- 
Rodrigo Vivi
Blog: http://blog.vivi.eng.br
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-11-02 23:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-03 22:56 [PATCH v5 2/5] drm/i915/guc : Removing i915_modparams.enable_guc_loading module Sujaritha Sundaresan
2017-10-04  6:45 ` Sagar Arun Kamble
2017-10-05  0:26   ` Sujaritha
2017-10-04 12:00 ` Michal Wajdeczko
2017-10-04 13:07 ` Joonas Lahtinen
2017-11-02 23:52   ` Rodrigo Vivi [this message]
2017-11-03  0:03     ` Chris Wilson
2017-11-03  8:36       ` Joonas Lahtinen
2017-11-03 17:08         ` Rodrigo Vivi
2017-11-06 10:24           ` Patch tag ordering (Was: Re: [PATCH v5 2/5] drm/i915/guc : Removing i915_modparams.enable_guc_loading module) Joonas Lahtinen
2017-11-06 11:41             ` 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=CABVU7+vW_E27hA_8H+iWUcs4_ufdUrqsZw_pauQLOPn_87K6xA@mail.gmail.com \
    --to=rodrigo.vivi@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=joonas.lahtinen@linux.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 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.