From: Igor Grinberg <grinberg@compulab.co.il>
To: "Pedanekar, Hemant" <hemantp@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Tony Lindgren <tony@atomide.com>,
"Hilman, Kevin" <khilman@ti.com>, Paul Walmsley <paul@pwsan.com>
Subject: Re: [PATCH v3 3/3] ARM: OMAP: TI814X: Create board support and enable build for TI8148 EVM
Date: Tue, 04 Oct 2011 11:00:44 +0200 [thread overview]
Message-ID: <4E8ACB3C.6020401@compulab.co.il> (raw)
In-Reply-To: <2A3DCF3DA181AD40BDE86A3150B27B6B03B4EC5D52@dbde02.ent.ti.com>
On 10/03/11 18:45, Pedanekar, Hemant wrote:
> Hi Igor,
>
> Igor Grinberg wrote on Sunday, October 02, 2011 5:38 PM:
>
>> Hi Hemant,
>>
>> On 09/29/11 04:09, Hemant Pedanekar wrote:
>>> This patch adds minimal support and build configuration for TI8148 EVM.
>>> Also adds support for low level debugging on UART1 console on the EVM.
>>>
>>> Note that existing TI8168 EVM file (board-ti8168evm.c) is updated with
>>> machine info for TI8148 EVM and renamed as board-ti81xxevm.c.
>>
>> Should we really rename the existing file?
>> Shouldn't we just stick to the name of the file submitted first?
>> (e.g. board-ti8168evm.c) and just add the support for the new
>> TI8148 EVM in to the existing file?
>
> But won't this be misleading?
Misleading? For whom?
Actually, I don't really care how you call that file.
What I care (and I think not just me) is uniformity, so
if we decide to rename all those files that have multiple
boards supported in them, I'm fine with it.
So pros for my proposed approach would be:
1) Currently, there are already board files with multiple boards
supported in them that follow the approach and renaming them is
really unnecessary.
2) git log will not break.
3) boards that cannot be named after the convention like 81xx
but can be added to the same file will not require further renaming
(like 82x8 - I don't really know if that will exist, just wondering).
4) This renaming is really what Linus likes ;)
cons:
1) Misleading?
Currently, I don't think this renaming is good for anything,
especially that majority of the board stuff should be transformed
to the DT descriptors.
--
Regards,
Igor.
next prev parent reply other threads:[~2011-10-04 9:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 1:09 [PATCH v3 3/3] ARM: OMAP: TI814X: Create board support and enable build for TI8148 EVM Hemant Pedanekar
2011-10-02 12:08 ` Igor Grinberg
2011-10-03 16:45 ` Pedanekar, Hemant
2011-10-04 9:00 ` Igor Grinberg [this message]
2011-10-04 9:41 ` Pedanekar, Hemant
2011-10-06 19:17 ` Tony Lindgren
2011-10-07 3:04 ` Pedanekar, Hemant
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=4E8ACB3C.6020401@compulab.co.il \
--to=grinberg@compulab.co.il \
--cc=hemantp@ti.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=tony@atomide.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