All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kever Yang <kever.yang@rock-chips.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/3] rockchip: correct ARCH_SOC name
Date: Thu, 28 Mar 2019 17:31:45 +0800	[thread overview]
Message-ID: <1a6ab3a4-7c9d-a2bb-be0d-3a2f3f79624a@rock-chips.com> (raw)
In-Reply-To: <09B44A88-1CB0-4D5B-8614-1A347D56F6D1@theobroma-systems.com>

Hi Philipp,


On 03/28/2019 03:02 PM, Philipp Tomsich wrote:
>
>> On 28.03.2019, at 04:01, Kever Yang <kever.yang@rock-chips.com> wrote:
>>
>> The ARCH_SOC name default as 'rockchip' and we put all the
>> header file in 'arch/arm/include/asm/arch-rockchip/', but
>> the 'rockchip' is not the SOC name, let's correct it after
>> we update all the source file.
>>
>> Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
> Reviewed-by: Philipp Tomsiich <philipp.tomsich@theobroma-systems.com>
>
> Just a style question: most of the documentation refers to the chips as RK3…
> while this has them as rk3… (i.e. the differenc eis whether the RK is lower-
> or upper-case); is this difference intentional?

This soc name will use to mach rk3...dtsi in source code, and all the
dtsi files are using lower-case.

Thanks,
- Kever
>
> Thanks,
> Phil.

  reply	other threads:[~2019-03-28  9:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-28  3:01 [U-Boot] [PATCH 0/3] rockchip: correct SYS_SOC name for all rockchip SoCs Kever Yang
2019-03-28  3:01 ` [U-Boot] [PATCH 1/3] rockchip: arm: use 'arch-rockchip' for common header Kever Yang
2019-03-28  7:02   ` Philipp Tomsich
2019-04-01  7:12   ` Neil Armstrong
2019-04-01 13:13     ` Tom Rini
2019-04-02  0:58       ` Kever Yang
2019-05-01 13:06   ` Philipp Tomsich
2019-03-28  3:01 ` [U-Boot] [PATCH 2/3] rockchip: use 'arch-rockchip' as header file path Kever Yang
2019-03-30 21:18   ` Simon Glass
2019-04-01  1:02     ` [U-Boot] [PATCH 2/3] rockchip: use 'arch-rockchip' as header file path【请注意，邮件由sjg@google.com代发】 Kever Yang
2019-04-01  2:00       ` Simon Glass
2019-04-01  2:46         ` Kever Yang
2019-04-01 19:00           ` Simon Glass
2019-04-02  1:11             ` Kever Yang
2019-04-05  2:33               ` Simon Glass
2019-04-03 19:57     ` [U-Boot] [PATCH 2/3] rockchip: use 'arch-rockchip' as header file path Simon Glass
2019-04-04 13:11       ` [U-Boot] [PATCH 2/3] rockchip: use 'arch-rockchip' as header file path【请注意，邮件由sjg@google.com代发】 Kever Yang
2019-04-05  2:33         ` Simon Glass
2019-04-28 23:34   ` [U-Boot] [PATCH 2/3] rockchip: use 'arch-rockchip' as header file path Philipp Tomsich
2019-05-01 13:06   ` Philipp Tomsich
2019-03-28  3:01 ` [U-Boot] [PATCH 3/3] rockchip: correct ARCH_SOC name Kever Yang
2019-03-28  7:02   ` Philipp Tomsich
2019-03-28  9:31     ` Kever Yang [this message]
2019-05-01 13:06   ` Philipp Tomsich

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=1a6ab3a4-7c9d-a2bb-be0d-3a2f3f79624a@rock-chips.com \
    --to=kever.yang@rock-chips.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.