From: Alessandro Zummo <a.zummo@towertech.it>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: zhangqing <zhangqing@rock-chips.com>,
heiko@sntech.de, lee.jones@linaro.org, huangtao@rock-chips.com,
zyw@rock-chips.com, linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org, rtc-linux@googlegroups.com
Subject: Re: [RESEND PATCH] rtc: rk808: rename rtc-rk808.c to rtc-rk8xx.c
Date: Mon, 4 Jan 2016 14:59:38 +0100 [thread overview]
Message-ID: <20160104145938.6c053b5a@linux.lan.towertech.it> (raw)
In-Reply-To: <20160104094546.GB32724@piout.net>
On Mon, 4 Jan 2016 10:45:46 +0100
Alexandre Belloni <alexandre.belloni@free-electrons.com> wrote:
> I'm not sure it is useful to do that renaming. It is usual to have one
> driver that supports multiple chips named with the forst chip it
> supported.
>
> Also, what would happen if for example rk855 is not compatible at all
> with the previous implementations?
Alexandre is absolutely right. There's no need to rename a driver,
it would just piss off people who are used to that name and
have it in their scripts. Like when your eth0 gets renamed
to some obscure enXXX <g>.
--
Best regards,
Alessandro Zummo - CEO,
Tower Technologies - Torino, Italy
http://www.towertech.it
WARNING: multiple messages have this Message-ID (diff)
From: Alessandro Zummo <a.zummo@towertech.it>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: zhangqing <zhangqing@rock-chips.com>,
heiko@sntech.de, lee.jones@linaro.org, huangtao@rock-chips.com,
zyw@rock-chips.com, linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org, rtc-linux@googlegroups.com
Subject: [rtc-linux] Re: [RESEND PATCH] rtc: rk808: rename rtc-rk808.c to rtc-rk8xx.c
Date: Mon, 4 Jan 2016 14:59:38 +0100 [thread overview]
Message-ID: <20160104145938.6c053b5a@linux.lan.towertech.it> (raw)
In-Reply-To: <20160104094546.GB32724@piout.net>
On Mon, 4 Jan 2016 10:45:46 +0100
Alexandre Belloni <alexandre.belloni@free-electrons.com> wrote:
> I'm not sure it is useful to do that renaming. It is usual to have one
> driver that supports multiple chips named with the forst chip it
> supported.
>
> Also, what would happen if for example rk855 is not compatible at all
> with the previous implementations?
Alexandre is absolutely right. There's no need to rename a driver,
it would just piss off people who are used to that name and
have it in their scripts. Like when your eth0 gets renamed
to some obscure enXXX <g>.
--
Best regards,
Alessandro Zummo - CEO,
Tower Technologies - Torino, Italy
http://www.towertech.it
--
--
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
---
You received this message because you are subscribed to the Google Groups "rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
WARNING: multiple messages have this Message-ID (diff)
From: Alessandro Zummo <a.zummo-BfzFCNDTiLLj+vYz1yj4TQ@public.gmane.org>
To: Alexandre Belloni
<alexandre.belloni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
Cc: huangtao-TNX95d0MmH7DzftRWevZcw@public.gmane.org,
heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org,
rtc-linux-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
zhangqing <zhangqing-TNX95d0MmH7DzftRWevZcw@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
zyw-TNX95d0MmH7DzftRWevZcw@public.gmane.org,
lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org
Subject: Re: [RESEND PATCH] rtc: rk808: rename rtc-rk808.c to rtc-rk8xx.c
Date: Mon, 4 Jan 2016 14:59:38 +0100 [thread overview]
Message-ID: <20160104145938.6c053b5a@linux.lan.towertech.it> (raw)
In-Reply-To: <20160104094546.GB32724-m++hUPXGwpdeoWH0uzbU5w@public.gmane.org>
On Mon, 4 Jan 2016 10:45:46 +0100
Alexandre Belloni <alexandre.belloni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org> wrote:
> I'm not sure it is useful to do that renaming. It is usual to have one
> driver that supports multiple chips named with the forst chip it
> supported.
>
> Also, what would happen if for example rk855 is not compatible at all
> with the previous implementations?
Alexandre is absolutely right. There's no need to rename a driver,
it would just piss off people who are used to that name and
have it in their scripts. Like when your eth0 gets renamed
to some obscure enXXX <g>.
--
Best regards,
Alessandro Zummo - CEO,
Tower Technologies - Torino, Italy
http://www.towertech.it
next prev parent reply other threads:[~2016-01-04 14:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-31 14:14 [RESEND PATCH] rtc: rk808: rename rtc-rk808.c to rtc-rk8xx.c zhangqing
2015-12-31 14:14 ` [rtc-linux] " zhangqing
2016-01-04 9:14 ` Kever Yang
2016-01-04 9:14 ` [rtc-linux] " Kever Yang
2016-01-04 9:45 ` Alexandre Belloni
2016-01-04 9:45 ` [rtc-linux] " Alexandre Belloni
2016-01-04 13:59 ` Alessandro Zummo [this message]
2016-01-04 13:59 ` Alessandro Zummo
2016-01-04 13:59 ` [rtc-linux] " Alessandro Zummo
2016-01-05 8:31 ` Huang, Tao
2016-01-05 8:31 ` [rtc-linux] " Huang, Tao
2016-01-05 8:54 ` Alexandre Belloni
2016-01-05 8:54 ` [rtc-linux] " Alexandre Belloni
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=20160104145938.6c053b5a@linux.lan.towertech.it \
--to=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=rtc-linux@googlegroups.com \
--cc=zhangqing@rock-chips.com \
--cc=zyw@rock-chips.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 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.