From: Dan Carpenter <dan.carpenter@oracle.com>
To: Justin Skists <justin.skists@juzza.co.uk>
Cc: devel@driverdev.osuosl.org, "Todd Kjos" <tkjos@android.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, "Arve Hjønnevåg" <arve@android.com>,
"Nathan Chancellor" <natechancellor@gmail.com>,
"Martijn Coenen" <maco@android.com>
Subject: Re: [PATCH 2/6] staging: android: Clean up license identifiers
Date: Mon, 14 May 2018 17:07:06 +0300 [thread overview]
Message-ID: <20180514140706.qjddnq5vrclf665w@mwanda> (raw)
In-Reply-To: <121696744.206121.1526305937025@email.1and1.co.uk>
On Mon, May 14, 2018 at 02:52:16PM +0100, Justin Skists wrote:
>
> > On 14 May 2018 at 14:29 Dan Carpenter <dan.carpenter@oracle.com> wrote:
> >
> >
> > On Sun, May 06, 2018 at 06:13:24PM -0700, Nathan Chancellor wrote:
> > > Add the identifiers when missing and fix the ones already present
> > > according to checkpatch.pl.
> > >
> > > Signed-off-by: Nathan Chancellor <natechancellor@gmail.com>
> > > ---
> > > drivers/staging/android/ashmem.h | 6 +-----
> > > drivers/staging/android/uapi/ashmem.h | 6 +-----
> > > drivers/staging/android/uapi/vsoc_shm.h | 10 +---------
> > > drivers/staging/android/vsoc.c | 11 +----------
> > > 4 files changed, 4 insertions(+), 29 deletions(-)
> > >
> > > diff --git a/drivers/staging/android/ashmem.h b/drivers/staging/android/ashmem.h
> > > index 60d7208f110a..1a478173cd21 100644
> > > --- a/drivers/staging/android/ashmem.h
> > > +++ b/drivers/staging/android/ashmem.h
> > > @@ -1,13 +1,9 @@
> > > -// SPDX-License-Identifier: (GPL-2.0 OR Apache-2.0)
> > > +/* SPDX-License-Identifier: GPL-2.0 OR Apache-2.0 */
> >
> >
> > // was correct for SPDX headers.
>
> Sorry, header files use the /* ... */ format. :)
>
> https://elixir.bootlin.com/linux/v4.17-rc5/source/Documentation/process/license-rules.rst
>
Oh. Huh... That's fine then. My bad.
regards,
dan carpenter
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2018-05-14 14:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 1:13 [PATCH 1/6] staging: android: Kconfig; Remove excessive hyphens Nathan Chancellor
2018-05-07 1:13 ` [PATCH 2/6] staging: android: Clean up license identifiers Nathan Chancellor
2018-05-14 13:29 ` Dan Carpenter
2018-05-14 13:51 ` Greg Kroah-Hartman
2018-05-14 13:52 ` Justin Skists
2018-05-14 14:07 ` Dan Carpenter [this message]
2018-05-07 1:13 ` [PATCH 3/6] staging: android: vsoc: Fix ending '(' warnings in function defintions Nathan Chancellor
2018-05-14 13:31 ` Dan Carpenter
2018-05-07 1:13 ` [PATCH 4/6] staging: android: vsoc: Fix ending '(' warnings in do_destroy_fd_scoped_permission Nathan Chancellor
2018-05-07 1:13 ` [PATCH 5/6] staging: android: vsoc: Fix ending '(' warnings in vsoc_ioctl Nathan Chancellor
2018-05-07 1:13 ` [PATCH 6/6] staging: android: vsoc: Fix ending '(' warnings in vsoc_probe_device Nathan Chancellor
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=20180514140706.qjddnq5vrclf665w@mwanda \
--to=dan.carpenter@oracle.com \
--cc=arve@android.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=justin.skists@juzza.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=natechancellor@gmail.com \
--cc=tkjos@android.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;
as well as URLs for NNTP newsgroup(s).