From: Till Harbaum / Lists <lists-RcHadlBFbzVAfugRpC6u6w@public.gmane.org>
To: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: Re: [PATCH] New VID/PID pair for i2c-tiny-usb
Date: Thu, 27 Mar 2008 20:47:21 +0100 [thread overview]
Message-ID: <200803272047.21505.lists@harbaum.org> (raw)
In-Reply-To: <20080326154415.2981961a-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
Hi,
Am Mittwoch 26 März 2008 schrieb Jean Delvare:
> Note: your e-mail client is wrapping long lines -> patch doesn't apply.
I thought i've verified that, but obviously it happened anyway.
> Please use a single /* */ pair for multi-line comments.
Ok
> Maybe I'm missing something obvious, but if you already have a device
> ID, what's the point of switching to another? The original ID is not
> going to be deprecated and/or used for something else, is it?
The original id was donated by ftdi without stating anywhere that the id has
to be used with their products. So i used it for the i2c-tiny-usb which
obviously isn't based on a ftdi chipset. I've been told that ftdi has changed
that policy lately. While i don't expect them to actually ask me not to use
their id without using the chips i thought it was clever to switch to an id
i've explicitely bought to avoid future problems with ftdis new policies.
I'll change the id from the ftdi ones to the ones i recently bought on all my
projects. Just to avoid future problems as early as possible.
Does this make sense?
Updated patch will follow.
Regards,
Till
_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c
next prev parent reply other threads:[~2008-03-27 19:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-24 9:42 [PATCH] New VID/PID pair for i2c-tiny-usb Till Harbaum / Lists
[not found] ` <200803241042.31263.lists-RcHadlBFbzVAfugRpC6u6w@public.gmane.org>
2008-03-26 14:44 ` Jean Delvare
[not found] ` <20080326154415.2981961a-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-03-27 19:47 ` Till Harbaum / Lists [this message]
[not found] ` <200803272047.21505.lists-RcHadlBFbzVAfugRpC6u6w@public.gmane.org>
2008-03-30 12:31 ` Jean Delvare
[not found] ` <20080330143107.1575e1bf-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-03-30 18:55 ` Till Harbaum / Lists
[not found] ` <200803302055.15948.lists-RcHadlBFbzVAfugRpC6u6w@public.gmane.org>
2008-03-30 19:53 ` Jean Delvare
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=200803272047.21505.lists@harbaum.org \
--to=lists-rchadlbfbzvafugrpc6u6w@public.gmane.org \
--cc=i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@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