All of lore.kernel.org
 help / color / mirror / Atom feed
From: Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>, Rob Herring <robh@kernel.org>,
	Leo Li <leoyang.li@nxp.com>, Shawn Guo <shawnguo@kernel.org>,
	"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
	<linux-arm-kernel@lists.infradead.org>
Subject: RE: [PATCH 1/2][RESEND] ARM: dts: Add big-endian in nor node for ls1021a
Date: Wed, 29 Aug 2018 02:55:47 +0000	[thread overview]
Message-ID: <VI1PR0402MB3854E14A0468CEFBDFDFE48B97090@VI1PR0402MB3854.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <CAOMZO5BVrK98ksQ2KBiXTy6O-nXjOG8_fFueRRXHZOwCMJ1UGg@mail.gmail.com>

Dear Fabio,

> -----Original Message-----
> From: Fabio Estevam <festevam@gmail.com>
> Sent: Wednesday, August 29, 2018 3:56 AM
> To: Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com>
> Cc: open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS
> <devicetree@vger.kernel.org>; Rob Herring <robh@kernel.org>; Mark
> Rutland <mark.rutland@arm.com>; Shawn Guo <shawnguo@kernel.org>;
> moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE <linux-arm-
> kernel@lists.infradead.org>; Leo Li <leoyang.li@nxp.com>
> Subject: Re: [PATCH 1/2][RESEND] ARM: dts: Add big-endian in nor node for
> ls1021a
> 
> On Tue, Aug 28, 2018 at 3:59 AM, Prabhakar Kushwaha
> <prabhakar.kushwaha@nxp.com> wrote:
> 
> > diff --git a/arch/arm/boot/dts/ls1021a-qds.dts
> > b/arch/arm/boot/dts/ls1021a-qds.dts
> > index 499f41a2c6f0..923a25760516 100644
> > --- a/arch/arm/boot/dts/ls1021a-qds.dts
> > +++ b/arch/arm/boot/dts/ls1021a-qds.dts
> > @@ -1,5 +1,6 @@
> >  /*
> >   * Copyright 2013-2014 Freescale Semiconductor, Inc.
> > + * Copyright 2018 NXP
> 
> This line is unrelated to the big-endian change.

Yes, this line is unrelated to this change.

Freeescale has been acquired by NXP in 2016. 
We want to add NXP copyright wherever freescale's copyright is present. But it is not possible in one-go.

So we are adding NXP copyright as and when any file having freescale's copyright  being touched.  

--pk

WARNING: multiple messages have this Message-ID (diff)
From: prabhakar.kushwaha@nxp.com (Prabhakar Kushwaha)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2][RESEND] ARM: dts: Add big-endian in nor node for ls1021a
Date: Wed, 29 Aug 2018 02:55:47 +0000	[thread overview]
Message-ID: <VI1PR0402MB3854E14A0468CEFBDFDFE48B97090@VI1PR0402MB3854.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <CAOMZO5BVrK98ksQ2KBiXTy6O-nXjOG8_fFueRRXHZOwCMJ1UGg@mail.gmail.com>

Dear Fabio,

> -----Original Message-----
> From: Fabio Estevam <festevam@gmail.com>
> Sent: Wednesday, August 29, 2018 3:56 AM
> To: Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com>
> Cc: open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS
> <devicetree@vger.kernel.org>; Rob Herring <robh@kernel.org>; Mark
> Rutland <mark.rutland@arm.com>; Shawn Guo <shawnguo@kernel.org>;
> moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE <linux-arm-
> kernel at lists.infradead.org>; Leo Li <leoyang.li@nxp.com>
> Subject: Re: [PATCH 1/2][RESEND] ARM: dts: Add big-endian in nor node for
> ls1021a
> 
> On Tue, Aug 28, 2018 at 3:59 AM, Prabhakar Kushwaha
> <prabhakar.kushwaha@nxp.com> wrote:
> 
> > diff --git a/arch/arm/boot/dts/ls1021a-qds.dts
> > b/arch/arm/boot/dts/ls1021a-qds.dts
> > index 499f41a2c6f0..923a25760516 100644
> > --- a/arch/arm/boot/dts/ls1021a-qds.dts
> > +++ b/arch/arm/boot/dts/ls1021a-qds.dts
> > @@ -1,5 +1,6 @@
> >  /*
> >   * Copyright 2013-2014 Freescale Semiconductor, Inc.
> > + * Copyright 2018 NXP
> 
> This line is unrelated to the big-endian change.

Yes, this line is unrelated to this change.

Freeescale has been acquired by NXP in 2016. 
We want to add NXP copyright wherever freescale's copyright is present. But it is not possible in one-go.

So we are adding NXP copyright as and when any file having freescale's copyright  being touched.  

--pk

  reply	other threads:[~2018-08-29  2:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-28  6:59 [PATCH] arm64: dts: remove big-endian filed from IFC controller Prabhakar Kushwaha
2018-08-28  6:59 ` Prabhakar Kushwaha
2018-08-28  6:59 ` [PATCH 1/2][RESEND] ARM: dts: Add big-endian in nor node for ls1021a Prabhakar Kushwaha
2018-08-28  6:59   ` Prabhakar Kushwaha
2018-08-28 20:46   ` Li Yang
2018-08-28 20:46     ` Li Yang
2018-08-28 22:25   ` Fabio Estevam
2018-08-28 22:25     ` Fabio Estevam
2018-08-29  2:55     ` Prabhakar Kushwaha [this message]
2018-08-29  2:55       ` Prabhakar Kushwaha
2018-09-02 23:58   ` Shawn Guo
2018-09-02 23:58     ` Shawn Guo
2018-08-28  6:59 ` [PATCH 2/2][RESEND] arm64: dts: Add big-endian in nor node for ls104xa Prabhakar Kushwaha
2018-08-28  6:59   ` Prabhakar Kushwaha
2018-08-28 20:44   ` Li Yang
2018-08-28 20:44     ` Li Yang
2018-08-28 22:26   ` Fabio Estevam
2018-08-28 22:26     ` Fabio Estevam
2018-08-28 18:38 ` [PATCH] arm64: dts: remove big-endian filed from IFC controller Li Yang
2018-08-28 18:38   ` Li Yang

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=VI1PR0402MB3854E14A0468CEFBDFDFE48B97090@VI1PR0402MB3854.eurprd04.prod.outlook.com \
    --to=prabhakar.kushwaha@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=leoyang.li@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=robh@kernel.org \
    --cc=shawnguo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.