All of lore.kernel.org
 help / color / mirror / Atom feed
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, 20 Dec 2013 09:36:00 -0800	[thread overview]
Message-ID: <87sitnh1bz.fsf@linaro.org> (raw)
In-Reply-To: <CAOesGMjaJVWoMWgywkHfeD+0TMw3pze40CAvTcuC7+NavMq22w@mail.gmail.com> (Olof Johansson's message of "Fri, 20 Dec 2013 08:50:26 -0800")

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

  reply	other threads:[~2013-12-20 17:36 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 [this message]
2013-12-23  1:09     ` 答复: " xuwei (O)
2014-01-07 22:54       ` Kevin Hilman
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=87sitnh1bz.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 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.