From: Vinod Koul <vkoul@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Dan Williams <dan.j.williams@intel.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Simon Horman <horms+renesas@verge.net.au>,
dmaengine@vger.kernel.org
Subject: dma: sh: convert to SPDX identifiers
Date: Wed, 12 Sep 2018 15:12:55 +0530 [thread overview]
Message-ID: <20180912094255.GI2766@vkoul-mobl> (raw)
On 11-09-18, 10:17, Geert Uytterhoeven wrote:
> Hi Vinod,
>
> On Tue, Sep 11, 2018 at 9:48 AM Vinod <vkoul@kernel.org> wrote:
> > On 07-09-18, 01:58, Kuninori Morimoto wrote:
> > > From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> > >
> > > This patch updates license to use SPDX-License-Identifier
> > > instead of verbose license text.
> >
> > Thanks but the style is not consistent in files :(
> >
> > Can we use one only?
>
> Please read
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/license-rules.rst#n69
>
> 2. Style:
>
> The SPDX license identifier is added in form of a comment. The comment
> style depends on the file type::
>
> C source: // SPDX-License-Identifier: <SPDX License Expression>
> C header: /* SPDX-License-Identifier: <SPDX License Expression> */
Right and I missed patch is doing for both c & h files, my bad
Applying this now.
Btw I have sent the series for dma_slave_config direction removal, sh/
drivers turned to be bit more, can you guys take care of it please?
next reply other threads:[~2018-09-12 9:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 9:42 Vinod Koul [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-12 12:09 dma: sh: convert to SPDX identifiers Vinod Koul
2018-09-12 12:05 Geert Uytterhoeven
2018-09-11 8:30 Kuninori Morimoto
2018-09-11 8:17 Geert Uytterhoeven
2018-09-11 7:48 Vinod Koul
2018-09-10 13:10 Simon Horman
2018-09-07 1:58 Kuninori Morimoto
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=20180912094255.GI2766@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=horms+renesas@verge.net.au \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-renesas-soc@vger.kernel.org \
/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