From: Andi Shyti <andi.shyti@samsung.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Philippe Ombredanne <pombredanne@nexb.com>,
Andi Shyti <andi@etezian.org>, Kukjin Kim <kgene@kernel.org>,
Mark Brown <broonie@kernel.org>,
linux-spi@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] spi: s3c64xx: add SPDX identifier
Date: Wed, 13 Dec 2017 10:48:54 +0900 [thread overview]
Message-ID: <20171213014854.GG20051@gangnam.samsung> (raw)
In-Reply-To: <CAJKOXPeCBPdCi2NnpBWimb4Py_zDZrsSK9o1cCswKM+XNeyqxQ@mail.gmail.com>
Hi Krzysztof,
> > Here, this should be as a top line:
> >
> > // SPDX-License-Identifier: GPL-2.0+
> >
> >
> > So I agree with the SPDX id but also pointing to the use of the C++ //
> > comment style as requested by Linus [1]
>
> Thanks for the reference. I see that Linus prefers converting entire
> comment into // style. I was not arguing about SPDX line but entire
> existing copyright comment which follows it:
>
> > +//
> > +// Copyright (c) 2009 Samsung Electronics Co., Ltd.
> > +// Jaswinder Singh <jassi.brar@samsung.com>
it just looks ugly to me to have something like
// SPDX...
/*
* Copyright (c)...
* Jasw...
*/
I would make everything of the '//' style (I've also seen that
this is the trend also in other subsystems), but honestly I don't
really care. If you're strong on not moving entirely in '//' style
then I can resend it with the double comment style.
Andi
P.S. About GPLv2 vs GPLv2+ I checked and I will repost it keeping
the license as its original. Thanks!
next prev parent reply other threads:[~2017-12-13 1:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20171212075830epcas2p31afc4a2e715e857694082748fd2bbe49@epcas2p3.samsung.com>
2017-12-12 7:58 ` Andi Shyti
2017-12-12 9:17 ` Krzysztof Kozlowski
2017-12-12 10:07 ` Mark Brown
2017-12-12 10:13 ` Krzysztof Kozlowski
2017-12-12 10:31 ` Mark Brown
2017-12-12 13:03 ` Andi Shyti
2017-12-12 13:45 ` Krzysztof Kozlowski
2017-12-12 14:48 ` Philippe Ombredanne
2017-12-12 15:00 ` Krzysztof Kozlowski
2017-12-12 15:24 ` Philippe Ombredanne
2017-12-12 15:35 ` Krzysztof Kozlowski
2017-12-13 1:48 ` Andi Shyti [this message]
2017-12-13 7:23 ` Krzysztof Kozlowski
2017-12-13 9:38 ` Mark Brown
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=20171213014854.GG20051@gangnam.samsung \
--to=andi.shyti@samsung.com \
--cc=andi@etezian.org \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=pombredanne@nexb.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®