From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Danielle Costantino
<danielle.costantino-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-i2c <linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Gerlando Falauto
<gerlando.falauto-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>,
Jean Delvare <jdelvare-l3A5Bk7waGM@public.gmane.org>,
Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>,
Martin Belanger
<martin.belanger-Ir6+u9MVKBtBDgjK7y7TUQ@public.gmane.org>,
Rodolfo Giometti
<giometti-AVVDYK/kqiJWk0Htik3J/w@public.gmane.org>,
Michael Lawnick <ml.lawnick-Mmb7MZpHnFY@public.gmane.org>,
Jeroen De Wachter
<jeroen.de.wachter-CNXmb7IdZIWZIoH1IeqzKA@public.gmane.org>
Subject: Re: [PATCH] i2c: mux: create "channel-n" symlinks for child segments
Date: Thu, 13 Nov 2014 14:41:28 +0100 [thread overview]
Message-ID: <20141113134128.GB8025@katana> (raw)
In-Reply-To: <CAAVjN7eG1D2fmu0gBqR8bwuo1i6e0XWju02JwVaO45YAr5qNkA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 702 bytes --]
On Wed, Nov 12, 2014 at 06:15:10AM -0800, Danielle Costantino wrote:
> Well the patch works (and is cleaner and uses slightly less resources
> and is how it should have been done originally)...but it breaks my
> current API (the path parsing will need to be modified) (parsing the
> parent device name (old fromat "i2c-%d" new "i2c-%d/%d-%04x" id to
> determine the parent adapter id). I can modify lsi2c to work with this
> new API, and it shouldn't be too difficult. But I cant update the tool
> until this is committed.
I've sent a V3 of the whole series a second ago. This one doesn't break
the ABI and should still help. Please let me know what you think by
replying to those patches, not here.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-11-13 13:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 12:36 [PATCH] i2c: mux: create "channel-n" symlinks for child segments Wolfram Sang
[not found] ` <1415363764-10821-1-git-send-email-wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
2014-11-07 21:10 ` Martin Belanger
2014-11-08 7:47 ` Danielle Costantino
[not found] ` <CAAVjN7dR0DYmuGOeMtVzsf-K7zsxXEY=jrGg_+V4XuyZhcyfiQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-11-08 17:51 ` Wolfram Sang
2014-11-12 12:29 ` Danielle Costantino
[not found] ` <CAAVjN7fJ0d2-Rp_9poPxMbrCVmz9be7-yZCE-Z7Vr=E4L8rpAg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-11-12 12:42 ` Wolfram Sang
2014-11-12 14:15 ` Danielle Costantino
[not found] ` <CAAVjN7eG1D2fmu0gBqR8bwuo1i6e0XWju02JwVaO45YAr5qNkA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-11-13 13:41 ` Wolfram Sang [this message]
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=20141113134128.GB8025@katana \
--to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
--cc=danielle.costantino-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=gerlando.falauto-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org \
--cc=giometti-AVVDYK/kqiJWk0Htik3J/w@public.gmane.org \
--cc=jdelvare-l3A5Bk7waGM@public.gmane.org \
--cc=jeroen.de.wachter-CNXmb7IdZIWZIoH1IeqzKA@public.gmane.org \
--cc=linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=martin.belanger-Ir6+u9MVKBtBDgjK7y7TUQ@public.gmane.org \
--cc=ml.lawnick-Mmb7MZpHnFY@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).