From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: 答复: [PATCH 1/3] ARM: hisi: rename hi3xxx to hisi
Date: Tue, 07 Jan 2014 14:54:01 -0800 [thread overview]
Message-ID: <87a9f7csja.fsf@linaro.org> (raw)
In-Reply-To: <8B36690B4C1B584EAD95DD4902A4FF37095E90C3@SZXEMA511-MBS.china.huawei.com> (xuwei's message of "Mon, 23 Dec 2013 01:09:48 +0000")
"xuwei (O)" <xuwei5@hisilicon.com> writes:
> Hi Olof and Kevin,
Hello.
Please don't top post (c.f. http://kernelnewbies.org/mailinglistguidelines)
> Please calm down.
>
> Both of us have a hard time to enable hi3xxx in kernel v3.14.
> Let me explain it.
I'm not sure an explanation is required, I understand the history here
pretty well. I've been involved in reviewing multiple versions of this
series. Also, I did lots of manual fixups for this series[1] which we
don't normally do.
> 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?
Yes, that's all fine and good. Nobody has objected to the rename
itself. In fact, we think it's better naming. Earlier reviews in the
series pointed out that the naming was messy and difficult to
understand.
What we've objected to was the timing and organization. I had just
merged the v12 series (after having to do a bunch of manual fixes) which
was a major pain. As soon as that was merged, the rename series was
sent.
The primary problem we have is that the rename is pointless churn.
Put simply, you should have done the rename in the original series much
earlier, not as an add-on series.
> And for hi3xxx SoCs, could you please keep it in the next?
I've just returned from 2 weeks off over the end of year holidays, and
I'm looking into it now, and not sure yet if it will make it for v3.14.
Kevin
[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2013-December/220168.html
> 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@lixom.net> writes:
>>
>> > On Thu, Dec 19, 2013 at 6:52 PM, Haojian Zhuang
>> > <haojian.zhuang@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
>>
next prev parent reply other threads:[~2014-01-07 22:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 2:52 [PATCH 1/3] ARM: hisi: rename hi3xxx to hisi Haojian Zhuang
2013-12-20 2:52 ` [PATCH 2/3] ARM: hisi: remove init_time Haojian Zhuang
2013-12-20 2:52 ` [PATCH 3/3] ARM: dts: rename hi4511 dts file Haojian Zhuang
2013-12-20 16:50 ` [PATCH 1/3] ARM: hisi: rename hi3xxx to hisi Olof Johansson
2013-12-20 17:36 ` Kevin Hilman
2013-12-23 1:09 ` 答复: " xuwei (O)
2014-01-07 22:54 ` Kevin Hilman [this message]
2014-01-10 16:31 ` Kevin Hilman
2014-01-08 0:58 ` Kevin Hilman
2014-01-08 1:16 ` Haojian Zhuang
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=87a9f7csja.fsf@linaro.org \
--to=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).