From: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
To: Bryan Wu <cooloney@gmail.com>
Cc: Jacek Anaszewski <j.anaszewski@samsung.com>,
Linux LED Subsystem <linux-leds@vger.kernel.org>,
Richard Purdie <rpurdie@rpsys.net>,
Sakari Ailus <sakari.ailus@iki.fi>
Subject: Re: [PATCH v2] leds: start numerating duplicated devices from 2
Date: Fri, 27 Mar 2015 08:51:01 +0100 [thread overview]
Message-ID: <CAPybu_1U7U04AKx3TF65PRw5KBLmp2uOJK3mn6mV=rup5m031w@mail.gmail.com> (raw)
In-Reply-To: <CAK5ve-JVeosdk+c7QsGqGWskNHvrpKbGn--LfGGOzwyROwDk0w@mail.gmail.com>
Hello Bryan
On Thu, Mar 26, 2015 at 7:15 PM, Bryan Wu <cooloney@gmail.com> wrote:
> No, I prefer to "_1" since normally we treat the first one "_0" or
> empty. But I suggest we add the "_0" for the first new device then the
> second one will be "_1"
Wouldn't that break the userspace API? perhaps there is a script/app
is using the legacy name.
What about leaving the legacy file, but adding a symbolic link from
name_0 to name?
Regards!
next prev parent reply other threads:[~2015-03-27 7:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 14:59 [PATCH v2] leds: start numerating duplicated devices from 2 Jacek Anaszewski
2015-03-26 18:15 ` Bryan Wu
2015-03-27 7:51 ` Ricardo Ribalda Delgado [this message]
2015-03-27 8:01 ` Jacek Anaszewski
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='CAPybu_1U7U04AKx3TF65PRw5KBLmp2uOJK3mn6mV=rup5m031w@mail.gmail.com' \
--to=ricardo.ribalda@gmail.com \
--cc=cooloney@gmail.com \
--cc=j.anaszewski@samsung.com \
--cc=linux-leds@vger.kernel.org \
--cc=rpurdie@rpsys.net \
--cc=sakari.ailus@iki.fi \
/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.