答复: [PATCH 1/3] ARM: hisi: rename hi3xxx to hisi

[xuwei (O)]

Hi Olof and Kevin,

Please calm down.
Both of us have a hard time to enable hi3xxx in kernel v3.14.
Let me explain it.

We have a new serial of SoCs for server market and they will named with hipxx.
And hi3xxx SoCs are for the mobile and STB market.
Now we hope to enable the hipxx SoCs in the kernel.
To make the "mach" directory simple, we hope hipxx SoCs could share the same directory with hi3xxx.
But according current situation, maybe we should add a new "mach" for the hipxx firstly.
Do you think is it OK?
 
And for hi3xxx SoCs, could you please keep it in the next?

Best Regards,
Wei Xu


> -----邮件原件-----
> 发件人: Kevin Hilman [mailto:khilman at linaro.org]
> 发送时间: 2013年12月21日 1:36
> 收件人: Olof Johansson
> 抄送: Haojian Zhuang; xuwei (O); Arnd Bergmann;
> linux-arm-kernel at lists.infradead.org; Haojian Zhuang
> 主题: Re: [PATCH 1/3] ARM: hisi: rename hi3xxx to hisi
> 
> Olof Johansson <olof at lixom.net> writes:
> 
> > On Thu, Dec 19, 2013 at 6:52 PM, Haojian Zhuang
> > <haojian.zhuang at linaro.org> wrote:
> >> Since some new Hisilicon SoCs are not named as hi3xxx, rename
> >> mach-hi3xxx to mach-hisi instead. And the pronounciation of "hisi" is
> >> similar to the chinese pronounciation of Hisilicon. So Hisilicon guys like this
> name.
> >>
> >> ARCH_HI3xxx will be renamed later since other drivers are using it
> >> and they are still in linux-next git tree. So rename ARCH_HI3xxx later.
> >>
> >
> > Are you kidding me? We JUST merge your platform after a very painful
> > review with many fumbly cycles, and the very first thing you do is
> > rename it?
> >
> > I even complained about the crazy numbering and naming, and you didn't
> > fix it while we were in review, and now just days after we merge the
> > patches this one comes out?
> >
> > For now, we'll drop your original branch and fold in these patches
> > with the original ones. There's no point in checking in a platform
> > just to rename it, so we'll do the fixups.
> 
> Agreed. I've dropped the hi3xxx/soc branch from next/soc and rebuild for-next
> without it.
> 
> Kevin
>