public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@xilinx.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/4] zynqmp: Kconfig: Move zynqmp Kconfig
Date: Mon, 15 Jun 2015 11:24:35 +0200	[thread overview]
Message-ID: <557E99D3.8000909@xilinx.com> (raw)
In-Reply-To: <CAK7LNAQYL4skSo9eOn1+F-=hOqk694+jgUupC6zYPXNv=xbYEA@mail.gmail.com>

On 06/15/2015 11:03 AM, Masahiro Yamada wrote:
> Hi Michal,
> 
> 
> 2015-06-15 17:53 GMT+09:00 Michal Simek <monstr@monstr.eu>:
>> On 06/10/2015 12:20 PM, Siva Durga Prasad Paladugu wrote:
>>> Move the zynqmp Kconfig from board to arch
>>> as there may be different boards under same
>>> architecture.
>>>
>>> Signed-off-by: Siva Durga Prasad Paladugu <sivadur@xilinx.com>
>>> ---
>>>  arch/arm/Kconfig                                   |    3 ++-
>>>  .../xilinx => arch/arm/cpu/armv8}/zynqmp/Kconfig   |    0
>>>  2 files changed, 2 insertions(+), 1 deletions(-)
>>>  rename {board/xilinx => arch/arm/cpu/armv8}/zynqmp/Kconfig (100%)
>>>
>>> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
>>> index 2985e6e..ca2c410 100644
>>> --- a/arch/arm/Kconfig
>>> +++ b/arch/arm/Kconfig
>>> @@ -850,6 +850,8 @@ source "arch/arm/mach-zynq/Kconfig"
>>>
>>>  source "arch/arm/cpu/armv7/Kconfig"
>>>
>>> +source "arch/arm/cpu/armv8/zynqmp/Kconfig"
>>> +
>>>  source "arch/arm/cpu/armv8/Kconfig"
>>>
>>>  source "arch/arm/imx-common/Kconfig"
>>> @@ -967,7 +969,6 @@ source "board/warp/Kconfig"
>>>  source "board/woodburn/Kconfig"
>>>  source "board/work-microwave/work_92105/Kconfig"
>>>  source "board/xaeniax/Kconfig"
>>> -source "board/xilinx/zynqmp/Kconfig"
>>>  source "board/zipitz2/Kconfig"
>>>
>>>  source "arch/arm/Kconfig.debug"
>>> diff --git a/board/xilinx/zynqmp/Kconfig b/arch/arm/cpu/armv8/zynqmp/Kconfig
>>> similarity index 100%
>>> rename from board/xilinx/zynqmp/Kconfig
>>> rename to arch/arm/cpu/armv8/zynqmp/Kconfig
>>>
>>
>> Masahiro/Simon: Can you see any problem with these patches?
> 
> I do not see any problem.
> 
> 
>> I want to make sure that we are align with your other activities.
> 
> I do not currently have any activities that could have conflicts with
> this series.

Ok great. Will wait for Simon if he has any concern. If not, I will
apply this series.

Thanks,
Michal

  reply	other threads:[~2015-06-15  9:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-10 10:20 [U-Boot] [PATCH 1/4] zynqmp: Kconfig: Move zynqmp Kconfig Siva Durga Prasad Paladugu
2015-06-10 10:20 ` [U-Boot] [PATCH 2/4] zynqmp: Define ep config for ZynqMP Siva Durga Prasad Paladugu
2015-06-10 10:20 ` [U-Boot] [PATCH 3/4] Kconfig: zynqMP: Move CONFIG_SYS_TEXT_BASE to defconfig Siva Durga Prasad Paladugu
2015-06-10 10:20 ` [U-Boot] [PATCH 4/4] zynqmp: Provide option to enable uart dcc support for zynqmp Siva Durga Prasad Paladugu
2015-06-15  8:53 ` [U-Boot] [PATCH 1/4] zynqmp: Kconfig: Move zynqmp Kconfig Michal Simek
2015-06-15  9:03   ` Masahiro Yamada
2015-06-15  9:24     ` Michal Simek [this message]
2015-06-16  2:45       ` Simon Glass
2015-06-16 13:59         ` Michal Simek

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=557E99D3.8000909@xilinx.com \
    --to=michal.simek@xilinx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox