public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 4/6] arm64: Add DTS support for FSL's LS2085A SoC
Date: Wed, 03 Sep 2014 20:34:54 +0200	[thread overview]
Message-ID: <3908508.RbGYaA1nXT@wuerfel> (raw)
In-Reply-To: <1409757194-28155-5-git-send-email-bhupesh.sharma@freescale.com>

On Wednesday 03 September 2014 20:43:12 Bhupesh Sharma wrote:
> diff --git a/arch/arm64/boot/dts/fsl-ls2085a-simu.dts b/arch/arm64/boot/dts/fsl-ls2085a-simu.dts
> new file mode 100644
> index 0000000..3c0f953
> --- /dev/null
> +++ b/arch/arm64/boot/dts/fsl-ls2085a-simu.dts
> @@ -0,0 +1,26 @@
> +/*
> + * Device Tree file for Freescale LS2085a software Simulator model
> + *
> + * Copyright (C) 2014, Freescale Semiconductor
> + *
> + * Bhupesh Sharma <bhupesh.sharma@freescale.com>
> + *
> + * This file is licensed under the terms of the GNU General Public
> + * License version 2.  This program is licensed "as is" without any
> + * warranty of any kind, whether express or implied.
> + */
> 

One more thing, same comment as for the respective Exynos7 patch:
can this please be a permissive license, like GPLv2+MIT dual
license?

	Arnd

  reply	other threads:[~2014-09-03 18:34 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-03 15:13 [PATCH V3 0/6] ARM64: Add support for FSL's LS2085A SoC Bhupesh Sharma
2014-09-03 15:13 ` [PATCH V3 1/6] Documentation: DT: Add bindings for FSL NS16550A UART Bhupesh Sharma
2014-09-03 15:13 ` [PATCH V3 2/6] Documentation: DT: Add entry for FSL LS2085A SoC and Simulator model Bhupesh Sharma
2014-09-03 15:13 ` [PATCH V3 3/6] Documentation: DT: Add entry for FSL Management Complex Bhupesh Sharma
2014-09-03 15:13 ` [PATCH V3 4/6] arm64: Add DTS support for FSL's LS2085A SoC Bhupesh Sharma
2014-09-03 18:34   ` Arnd Bergmann [this message]
2014-09-04  7:55     ` bhupesh.sharma at freescale.com
2014-09-20 20:35     ` bhupesh.sharma at freescale.com
2014-09-03 15:13 ` [PATCH V3 5/6] arm64: dts/Makefile: Add support for FSL's LS2085A simulator model Bhupesh Sharma
2014-09-03 15:13 ` [PATCH V3 6/6] arm64: Add support for FSL's LS2085A SoC in Kconfig and defconfig Bhupesh Sharma
2014-09-03 15:29 ` [PATCH V3 0/6] ARM64: Add support for FSL's LS2085A SoC Arnd Bergmann
2014-09-03 15:36   ` bhupesh.sharma at freescale.com
2014-09-03 15:39     ` Arnd Bergmann
2014-09-03 15:42       ` bhupesh.sharma at freescale.com
2014-09-03 15:56       ` Mark Rutland
2014-09-03 16:05         ` Arnd Bergmann
2014-09-03 16:09           ` Mark Rutland
2014-09-03 16:10             ` bhupesh.sharma at freescale.com
2014-09-03 16:18             ` Arnd Bergmann
2014-09-03 16:31               ` Mark Rutland
2014-09-03 18:31                 ` Arnd Bergmann
2014-09-04  9:13                   ` Mark Rutland
2014-09-04  9:39                     ` Arnd Bergmann
2014-09-04 16:32                       ` Stuart Yoder
2014-09-09 11:46                       ` bhupesh.sharma at freescale.com
2014-09-09 13:42                         ` Catalin Marinas
2014-09-20 20:35                       ` bhupesh.sharma at freescale.com
2014-09-22 13:55                         ` Mark Rutland
2014-09-24 14:50                       ` Stuart Yoder
2014-09-03 18:30         ` Geoff Levand

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=3908508.RbGYaA1nXT@wuerfel \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.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