linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jdelvare@suse.de (Jean Delvare)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/3] cpufreq: mediatek: Add support of cpufreq to MT2701/MT7623 SoC
Date: Mon, 17 Jul 2017 10:05:50 +0200	[thread overview]
Message-ID: <20170717100550.29c6b3d3@endymion> (raw)
In-Reply-To: <1499918078.2392.14.camel@mtksdaap41>

On Thu, 13 Jul 2017 11:54:38 +0800, Eddie Huang wrote:
> On Thu, 2017-07-13 at 08:46 +0530, Viresh Kumar wrote:
> > I am fine with both. Maybe don't resend for just that, mediatek
> > doesn't sound any bad.  
> 
> I am also fine with both. I think most people won't confuse about mtk
> and mediatek. I don't like send patches to just only change filenames
> and kconfig, especially kconfig modification will affect project
> defconfigs. My point is we shouldn't spend much time on this topic, and
> revisit filename when that driver need support new SoC, like this case.

I believe that being consistent is important, and I believe that
3-letter abbreviations are confusing. So in my ideal fantasy world, all
these drivers would be named *mediatek* and their config options would
be CONFIG_*MEDIATEK*. That being said, it's only my general opinion on
the topic. I'm not going to send any patch to rename any of these
drivers, as I have many tasks of higher priority on my own plate. And I
agree that renaming existing drivers does have a cost as well. So
whatever is decided is fine with me, really.

-- 
Jean Delvare
SUSE L3 Support

  reply	other threads:[~2017-07-17  8:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-10 14:23 [PATCH v4 0/3] some fixups for MediaTek cpufreq driver sean.wang at mediatek.com
2017-07-10 14:23 ` [PATCH v4 1/3] cpufreq: mediatek: Add support of cpufreq to MT2701/MT7623 SoC sean.wang at mediatek.com
2017-07-11  2:49   ` Eddie Huang
2017-07-12 14:50     ` Matthias Brugger
2017-07-13  3:16       ` Viresh Kumar
2017-07-13  3:54         ` Eddie Huang
2017-07-17  8:05           ` Jean Delvare [this message]
2017-07-17  8:06   ` Jean Delvare
2017-07-10 14:23 ` [PATCH v4 2/3] dt-bindings: cpufreq: move MediaTek cpufreq dt-bindings document to proper place sean.wang at mediatek.com
2017-07-10 14:23 ` [PATCH v4 3/3] dt-bindings: cpufreq: enhance MediaTek cpufreq dt-binding document sean.wang at mediatek.com
2017-07-17  6:16 ` [PATCH v4 0/3] some fixups for MediaTek cpufreq driver Sean Wang
2017-07-17  7:35   ` Viresh Kumar
2017-07-17 11:33     ` Rafael J. Wysocki

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=20170717100550.29c6b3d3@endymion \
    --to=jdelvare@suse.de \
    --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).