From: Jani Nikula <jani.nikula@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/i915: Move LRC register offsets to a header file
Date: Wed, 24 Jan 2018 12:13:31 +0200 [thread overview]
Message-ID: <87k1w77ees.fsf@intel.com> (raw)
In-Reply-To: <151672488291.13096.8710698940199524798@mail.alporthouse.com>
On Tue, 23 Jan 2018, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> Quoting Lucas De Marchi (2018-01-23 16:06:16)
>> On Tue, Jan 23, 2018 at 08:48:01AM +0000, Chris Wilson wrote:
>> > Quoting Michel Thierry (2018-01-23 00:41:07)
>> > > On 1/22/2018 4:31 PM, Lucas De Marchi wrote:
>> > > > So for this file what I understand is that it should be:
>> > > >
>> > > > // SPDX-License-Identifier: MIT
>> > > > // Copyright (C) 2014-2018 Intel Corporation
>> > >
>> > > So be it.
>> >
>> > Oh no, we don't do C++ comments.
>>
>> We drm or we kernel devs?
>>
>> $ git grep "// SPDX"| wc -l
>> 4487
>>
>> The suggestion was actually from Linus in the thread I linked. Quoting
>> here:
>>
>> > So in general, the _hope_ is that we can just end up replacing
>> > existing boilerplate comments with that single line SPDX comment
>> > (using "//" in *.[ch] files, but obviously some other kinds of files
>> > end up having a different comment character, typically '#').
>> ...
>> > And yes, feel free to replace block comments with // while at it.
>> ...
>> > We already have something like 700 different versions of the same
>> > silly copyright license boiler-plate due to typos, whitespace
>> > differences, comment style choices, yadda yadda. Let's avoid that mess
>> > by just picking _one_ single format and placement for the SPDX line.
>>
>> Which I agree with, hence my suggestion. Let me know if it should be
>> different in drm/
>
> Being consistent is far more important.
> Documentation/process/coding-style.rst is what we follow, breaking the
> rule and being inconsistent for copyright headers doesn't make any sense.
Please use /* */ rather than // in i915 throughout.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology 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-01-24 10:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 20:06 [PATCH] drm/i915: Move LRC register offsets to a header file Michel Thierry
2018-01-22 20:14 ` Chris Wilson
2018-01-22 20:26 ` Michel Thierry
2018-01-22 20:26 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-01-22 20:32 ` [PATCH v2] " Michel Thierry
2018-01-22 20:56 ` Lucas De Marchi
2018-01-22 21:28 ` Michal Wajdeczko
2018-01-22 21:49 ` Michel Thierry
2018-01-23 0:31 ` Lucas De Marchi
2018-01-23 0:41 ` Michel Thierry
2018-01-23 8:48 ` Chris Wilson
2018-01-23 16:06 ` Lucas De Marchi
2018-01-23 16:18 ` Michal Wajdeczko
2018-01-23 16:27 ` Lucas De Marchi
2018-01-23 16:28 ` Chris Wilson
2018-01-24 10:13 ` Jani Nikula [this message]
2018-01-22 20:54 ` ✓ Fi.CI.BAT: success for drm/i915: Move LRC register offsets to a header file (rev2) Patchwork
2018-01-23 0:41 ` [PATCH v3] drm/i915: Move LRC register offsets to a header file Michel Thierry
2018-01-23 1:00 ` ✓ Fi.CI.BAT: success for drm/i915: Move LRC register offsets to a header file (rev3) Patchwork
2018-01-23 7:46 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-01-23 19:50 ` [PATCH v4] drm/i915: Move LRC register offsets to a header file Michel Thierry
2018-01-23 20:57 ` Chris Wilson
2018-01-23 20:09 ` ✓ Fi.CI.BAT: success for drm/i915: Move LRC register offsets to a header file (rev4) Patchwork
2018-01-24 4:52 ` ✓ Fi.CI.IGT: " 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=87k1w77ees.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.demarchi@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.