All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Eddy Petrișor" <eddy.petrisor@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v5 0/2] Initial support for s32v234
Date: Sun, 5 Jun 2016 02:59:20 +0300	[thread overview]
Message-ID: <CAK0XTWf6=fqzyT47GN+v=Ovj7iBCjVc5YR5M-yXyhpb1=1jh7A@mail.gmail.com> (raw)
In-Reply-To: <CAOMZO5B4cmxCRSuKiaBMEZrjuwo5hzJbqE=-75X+KjXg5GMYZQ@mail.gmail.com>

2016-06-05 1:23 GMT+03:00 Fabio Estevam <festevam@gmail.com>:
> On Sat, Jun 4, 2016 at 4:18 PM, Eddy Petri?or <eddy.petrisor@nxp.com> wrote:
>
>>  board/freescale/s32v234evb/Kconfig              |  23 ++
>
> What about placing the files under board/nxp instead?

The board has been having support in our vendor branch a lot before
the Freescale - NXP unification/aquisition. Since the device trees
should not be changed, we consider that moving the board under nxp is
incompatible with the "don't make destructive changes in DTS"
requirement.

-- 
Eddy Petri?or

  reply	other threads:[~2016-06-04 23:59 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-03  0:10 [U-Boot] [PATCH 1/2] serial: Introduce linflex uart support Eddy Petrișor
2016-04-03  0:10 ` [U-Boot] [PATCH 2/2] armv8: s32v234: Introduce basic support for s32v234evb Eddy Petrișor
2016-04-19 16:53   ` Tom Rini
2016-04-21 16:03     ` Eddy Petrișor
2016-04-21 16:28       ` Tom Rini
2016-04-04  3:22 ` [U-Boot] [PATCH 1/2] serial: Introduce linflex uart support Bin Meng
2016-04-04 14:22   ` Eddy Petrișor
2016-04-05  1:43     ` Bin Meng
2016-04-27 22:07       ` [U-Boot] [PATCH v2 " Eddy Petrișor
2016-05-07 14:56         ` Bin Meng
2016-05-08  0:05           ` Eddy Petrișor
2016-04-27 21:39 ` [U-Boot] [PATCH 0/2] Initial support for S32V234 - version 2 Eddy Petrișor
2016-04-27 21:39 ` [U-Boot] [PATCH 1/2] serial: Introduce linflex uart support Eddy Petrișor
2016-04-27 21:39 ` [U-Boot] [PATCH 2/2] armv8: s32v234: Introduce basic support for s32v234evb Eddy Petrișor
2016-04-27 22:07 ` [U-Boot] [PATCH v2 0/2] Initial S32V234 support - version 2 (with notes now) Eddy Petrișor
2016-05-28  9:56   ` [U-Boot] [PATCH v3 0/2] Initial support for S32V234 - version 3 Eddy Petrișor
2016-05-28  9:56     ` [U-Boot] [PATCH v3 1/2] serial: Introduce linflex uart support Eddy Petrișor
2016-05-28  9:56     ` [U-Boot] [PATCH v3 2/2] armv8: s32v234: Introduce basic support for s32v234evb Eddy Petrișor
2016-05-28 10:10       ` Alexander Graf
2016-05-28 10:51     ` [U-Boot] [PATCH v4 0/2] Initial support for s32v234 Eddy Petrișor
2016-05-28 10:51       ` [U-Boot] [PATCH v4 1/2] serial: Introduce linflex uart support Eddy Petrișor
2016-05-28 10:51       ` [U-Boot] [PATCH v4 2/2] armv8: s32v234: Introduce basic support for s32v234evb Eddy Petrișor
2016-06-04 19:18     ` [U-Boot] [PATCH v5 0/2] Initial support for s32v234 Eddy Petrișor
2016-06-04 19:18       ` [U-Boot] [PATCH v5 1/2] serial: Introduce linflex uart support Eddy Petrișor
2016-06-04 19:18       ` [U-Boot] [PATCH v5 2/2] armv8: s32v234: Introduce basic support for s32v234evb Eddy Petrișor
2016-06-04 22:23       ` [U-Boot] [PATCH v5 0/2] Initial support for s32v234 Fabio Estevam
2016-06-04 23:59         ` Eddy Petrișor [this message]
2016-06-05  0:52           ` Fabio Estevam
2016-06-05  1:15             ` Eddy Petrișor
2016-06-05  0:42       ` [U-Boot] [PATCH v6 " Eddy Petrișor
2016-06-05  0:42         ` [U-Boot] [PATCH v6 1/2] serial: Introduce linflex uart support Eddy Petrișor
2016-06-19 14:10           ` [U-Boot] [U-Boot, v6, " Tom Rini
2016-06-19 20:41             ` Eddy Petrișor
2016-06-05  0:43         ` [U-Boot] [PATCH v6 2/2] armv8: s32v234: Introduce basic support for s32v234evb Eddy Petrișor
2016-06-19 14:10           ` [U-Boot] [U-Boot, v6, " Tom Rini
2016-06-19 20:51             ` Eddy Petrișor
2016-04-27 22:07 ` [U-Boot] [PATCH v2 " Eddy Petrișor
2016-05-07 16:22   ` Alexander Graf
2016-05-07 23:59     ` Eddy Petrișor
2016-05-08  7:21       ` Alexander Graf

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='CAK0XTWf6=fqzyT47GN+v=Ovj7iBCjVc5YR5M-yXyhpb1=1jh7A@mail.gmail.com' \
    --to=eddy.petrisor@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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.