DMA Engine development
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Angelo Dureghello <angelo@sysam.it>
Cc: dmaengine@vger.kernel.org, linux-m68k@vger.kernel.org
Subject: [v5,1/2] dmaengine: fsl-edma: extract common fsl-edma code (no changes in behavior intended)
Date: Thu, 28 Jun 2018 11:41:25 +0530	[thread overview]
Message-ID: <20180628061125.GP22377@vkoul-mobl> (raw)

On 22-06-18, 11:44, Angelo Dureghello wrote:

> ---
>  drivers/dma/Makefile          |   2 +-
>  drivers/dma/fsl-edma-common.c | 683 +++++++++++++++++++++++++++++++
>  drivers/dma/fsl-edma-common.h | 175 ++++++++
>  drivers/dma/fsl-edma.c        | 739 ++--------------------------------

use git format -M, that will help with renames

> +// SPDX-License-Identifier: GPL-2.0
> +// Copyright (c) 2013-2014 Freescale Semiconductor, Inc
> +// Copyright (c) 2017 Sysam, Angelo Dureghello  <angelo@sysam.it>
> +/*
> + * drivers/dma/fsl-edma-common.c
> + *
> + * Common code for Freescale the edma 32 or 64 channel version.
> + *
> + * This program is free software; you can redistribute it and/or
> + * modify it under the terms of the GNU General Public License as
> + * published by the Free Software Foundation version 2.
> + *
> + * This program is distributed "as is" WITHOUT ANY WARRANTY of any
> + * kind, whether express or implied; without even the implied warranty
> + * of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
> + * GNU General Public License for more details.
> + */

should we add this text, SPDX tag suffices

             reply	other threads:[~2018-06-28  6:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-28  6:11 Vinod Koul [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-06-22  9:44 [v5,1/2] dmaengine: fsl-edma: extract common fsl-edma code (no changes in behavior intended) Angelo Dureghello

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=20180628061125.GP22377@vkoul-mobl \
    --to=vkoul@kernel.org \
    --cc=angelo@sysam.it \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-m68k@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