From: eric.y.miao@gmail.com (Eric Miao)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/5] PalmGSM: generalisation of Treo680 code to PalmGSM
Date: Tue, 01 Sep 2009 17:39:47 +0800 [thread overview]
Message-ID: <4A9CEBE3.6090203@gmail.com> (raw)
In-Reply-To: <200909010322.49142.marek.vasut@gmail.com>
Marek Vasut wrote:
> Dne ?t 1. z??? 2009 02:07:16 Pavel Machek napsal(a):
>> Ahoj! / Hi!
> Ahoj! / Hi! / Guten Tag!
>>>>>>> arch/arm/mach-pxa/Kconfig | 5 +
>>>>>>> arch/arm/mach-pxa/Makefile | 2 +-
>>>>>>> arch/arm/mach-pxa/include/mach/palmgsm.h | 60 ++++
>>>>>>> arch/arm/mach-pxa/include/mach/treo680.h | 49 ---
>>>>>>> arch/arm/mach-pxa/palmgsm.c | 559
>>>>>>> ++++++++++++++++++++++++++++++ arch/arm/mach-pxa/treo680.c
>>>>>>> | 528 ----------------------------
>>>>>> I don't actually care too much about the naming - as long as 685
>>>>>> can stay within treo680.c, I don't see any problem with that. The
>>>>>> real question is: is palmgsm.c the proper name for all these
>>>>>> devices?
>>>>> Well, actually your completely right. PalmGSM is not fitting for all
>>>>> devices to come, more fitting would be something like Palm
>>>>> smartphones because there are CDMA devices to come too. On the other
>>>>> hand, this name is the best I found so far. If you don't mind I would
>>>>> even so...
>>>> I believe treo680 was better name then. Don't change it if you don't
>>>> need to...
>>> But I need to have different generic name - treo680 will be occupied by
>>> Treo680 specific stuff, which makes more sense, doesn't it?
>> And rename generic code to treo.c? Then you could have treo.c for
>> generic code, and treo680.c / treo685.c for specific models...
>>
>> palmgsm.c sounds like driver for their GSM chip...
>> Pavel
>
> Yeah, or treo-common.c in case you'd want to split it into core file + model
> files. But treo.c/palm(smart)phone.c (?) seems more ok. I dont like the idea of
> splitting the code into more files (one big, and many small).
>
Well, treo680.c can just include all the specific stuffs in a single
file as long as possibility is concerned. And #ifdef .. #endif can
be used to include the code or not. See ezx.c for a good example.
> Cheers!
next prev parent reply other threads:[~2009-09-01 9:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 0:43 update Treo680, generalise it and add Centro support Tomáš Čech
2009-08-27 0:43 ` [PATCH 1/5] Treo680: pxamci simplify to use GPIO Tomáš Čech
2009-08-27 0:43 ` [PATCH 2/5] Treo680: remove unused LCD power GPIO Tomáš Čech
2009-08-27 0:43 ` [PATCH 3/5] Treo680: fix freed GPIO in treo680_irda_shutdown() Tomáš Čech
2009-08-27 0:43 ` [PATCH 4/5] PalmGSM: generalisation of Treo680 code to PalmGSM Tomáš Čech
2009-08-27 0:43 ` [PATCH 5/5] PalmGSM: add basic Centro support Tomáš Čech
2009-08-27 13:35 ` Marek Vasut
2009-08-28 20:18 ` Tomáš 'Sleep_Walker' Čech
2009-08-27 2:31 ` [PATCH 4/5] PalmGSM: generalisation of Treo680 code to PalmGSM Eric Miao
2009-08-28 20:13 ` Tomáš 'Sleep_Walker' Čech
2009-08-31 10:43 ` Pavel Machek
2009-08-31 11:06 ` Tomáš 'Sleep_Walker' Čech
2009-09-01 0:07 ` Pavel Machek
2009-09-01 1:22 ` Marek Vasut
2009-09-01 9:39 ` Eric Miao [this message]
2009-09-01 20:50 ` Tomáš 'Sleep_Walker' Čech
2009-09-01 10:56 ` Tomáš 'Sleep_Walker' Čech
2009-08-31 10:44 ` [PATCH 1/5] Treo680: pxamci simplify to use GPIO Pavel Machek
2009-08-31 11:03 ` Tomáš 'Sleep_Walker' Čech
-- strict thread matches above, loose matches on Subject: below --
2009-08-31 17:25 update Treo680, generalise it and add Centro support - round 2 Tomáš Čech
2009-08-31 17:25 ` [PATCH 1/5] Treo680: pxamci simplify to use GPIO Tomáš Čech
2009-08-31 17:25 ` [PATCH 2/5] Treo680: remove unused LCD power GPIO Tomáš Čech
2009-08-31 17:25 ` [PATCH 3/5] Treo680: fix freed GPIO in treo680_irda_shutdown() Tomáš Čech
2009-08-31 17:26 ` [PATCH 4/5] PalmGSM: generalisation of Treo680 code to PalmGSM Tomáš Čech
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=4A9CEBE3.6090203@gmail.com \
--to=eric.y.miao@gmail.com \
--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.