From: khilman@linaro•org (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: 答复: [PATCH 1/3] ARM: hisi: rename hi3xxx to hisi
Date: Fri, 10 Jan 2014 08:31:28 -0800 [thread overview]
Message-ID: <878uunbxy7.fsf@linaro.org> (raw)
In-Reply-To: <87a9f7csja.fsf@linaro.org> (Kevin Hilman's message of "Tue, 07 Jan 2014 14:54:01 -0800")
Kevin Hilman <khilman@linaro•org> writes:
> "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.
The original hi3xxx series *plus* the rename is now merged into next/soc
for v3.14.
Kevin
next prev parent reply other threads:[~2014-01-10 16:31 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
2014-01-10 16:31 ` Kevin Hilman [this message]
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=878uunbxy7.fsf@linaro.org \
--to=khilman@linaro$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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