From: David Daney <ddaney.cavm@gmail.com>
To: James Hogan <james.hogan@imgtec.com>
Cc: Deng-Cheng Zhu <dengcheng.zhu@imgtec.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Gleb Natapov <gleb@kernel.org>,
kvm@vger.kernel.org, Sanjay Lal <sanjayl@kymasys.com>,
Ralf Baechle <ralf@linux-mips.org>,
Linux MIPS Mailing List <linux-mips@linux-mips.org>
Subject: Re: [PATCH v4 5/7] MIPS: KVM: Rename files to remove the prefix "kvm_" and "kvm_mips_"
Date: Thu, 26 Jun 2014 17:32:22 -0700 [thread overview]
Message-ID: <53ACBB96.9030803@gmail.com> (raw)
In-Reply-To: <CAAG0J99aDdsku1ZXX=aBxK4NVwEZK2wa+gV638yZN735qZnT+A@mail.gmail.com>
On 06/26/2014 04:21 PM, James Hogan wrote:
> On 26 June 2014 22:55, David Daney <ddaney.cavm@gmail.com> wrote:
>>>> There is precedence in x86 for some of the names though.
>>>>
>>>> But really why churn up the code in the first place? the kvm_mips
>>>> prefix does tell us exactly what we are dealing with.
>>>
>>>
>>> That's why people created the arch/mips/kvm directory, isn't it?
>>
>>
>> No. Segregating things into directories keeps code related to one
>> functional area together.
>>
>> File names are different. They should carry as much meaning as possible.
>>
>> For examples of this look at some of these directories:
>>
>> drivers/net/ethernet/intel/ixgb
>> drivers/i2c/busses
>>
>> It is not bad to have a filename prefix related to the function of the
>> files.
>
> Hi David,
>
> More importantly if you look in arch/*/kvm/, very few of the files
> have kvm in their names except for mips.
>
> Personally I find the filenames Deng-Cheng is suggesting must less
> cumbersome to type. Most of the files start with kvm_mips_ at the
> moment, which is completely redundant.
>
> As for churn, renaming the files hardly produces much churn compared
> to cleaning up coding style issues like some of the other patches, but
> I still think even they are worth doing.
I have expressed my opinion. I don't want to spend any more time on it.
Let the maintainers decide what they want to do.
David Daney
next prev parent reply other threads:[~2014-06-27 0:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 19:11 [PATCH v4 0/7] MIPS: KVM: Bugfixes and cleanups Deng-Cheng Zhu
2014-06-26 19:11 ` Deng-Cheng Zhu
2014-06-26 19:11 ` [PATCH v4 1/7] MIPS: KVM: Reformat code and comments Deng-Cheng Zhu
2014-06-26 19:11 ` Deng-Cheng Zhu
2014-06-26 19:11 ` [PATCH v4 2/7] MIPS: KVM: Use KVM internal logger Deng-Cheng Zhu
2014-06-26 19:11 ` Deng-Cheng Zhu
2014-06-26 19:11 ` [PATCH v4 3/7] MIPS: KVM: Simplify functions by removing redundancy Deng-Cheng Zhu
2014-06-26 19:11 ` Deng-Cheng Zhu
2014-06-26 19:11 ` [PATCH v4 4/7] MIPS: KVM: Remove unneeded volatile Deng-Cheng Zhu
2014-06-26 19:11 ` Deng-Cheng Zhu
2014-06-26 19:11 ` [PATCH v4 5/7] MIPS: KVM: Rename files to remove the prefix "kvm_" and "kvm_mips_" Deng-Cheng Zhu
2014-06-26 19:11 ` Deng-Cheng Zhu
2014-06-26 19:28 ` David Daney
2014-06-26 19:55 ` Deng-Cheng Zhu
2014-06-26 19:55 ` Deng-Cheng Zhu
2014-06-26 21:55 ` David Daney
2014-06-26 22:44 ` Deng-Cheng Zhu
2014-06-26 22:44 ` Deng-Cheng Zhu
2014-06-26 23:53 ` Deng-Cheng Zhu
2014-06-26 23:53 ` Deng-Cheng Zhu
2014-06-27 14:27 ` Paolo Bonzini
2014-06-26 23:21 ` James Hogan
2014-06-27 0:32 ` David Daney [this message]
2014-06-26 19:11 ` [PATCH v4 6/7] MIPS: KVM: Skip memory cleaning in kvm_mips_commpage_init() Deng-Cheng Zhu
2014-06-26 19:11 ` Deng-Cheng Zhu
2014-06-26 19:11 ` [PATCH v4 7/7] MIPS: KVM: Remove dead code of TLB index error in kvm_mips_emul_tlbwr() Deng-Cheng Zhu
2014-06-26 19:11 ` Deng-Cheng Zhu
2014-06-27 14:22 ` [PATCH v4 0/7] MIPS: KVM: Bugfixes and cleanups James Hogan
2014-06-27 14:22 ` James Hogan
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=53ACBB96.9030803@gmail.com \
--to=ddaney.cavm@gmail.com \
--cc=dengcheng.zhu@imgtec.com \
--cc=gleb@kernel.org \
--cc=james.hogan@imgtec.com \
--cc=kvm@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=pbonzini@redhat.com \
--cc=ralf@linux-mips.org \
--cc=sanjayl@kymasys.com \
/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