From: Kumar Gala <galak@kernel.crashing.org>
To: Jean Delvare <khali@linux-fr.org>
Cc: linuxppc-dev@ozlabs.org, i2c@lm-sensors.org
Subject: Re: [i2c] [PATCH 3/5] powerpc: Document device nodes for I2C devices.
Date: Fri, 18 May 2007 11:24:57 -0500 [thread overview]
Message-ID: <D50C4D36-CEA5-4F7F-8A4C-CC747DF85865@kernel.crashing.org> (raw)
In-Reply-To: <20070518171555.543f9bdc@hyperion.delvare>
On May 18, 2007, at 10:15 AM, Jean Delvare wrote:
> Hi Kumar,
>
> On Thu, 17 May 2007 12:21:02 -0500, Kumar Gala wrote:
>> The only support we have for i2c controllers is to support one
>> specific i2c controller from Freescale.
>>
>> If you aren't going to provide a complete solution why are you
>> prosing one? I'm tired of this put stuff in the device tree but only
>> as much as I need to do my particular thing.
>
> This is exactly how free software development works. If people were
> only proposing complete solutions, Linux would not even exist. Things
> happen exactly because people write what they need and contribute what
> they wrote. If you think it's not enough for your own needs
> (present or
> future), then _you_ get to do the extra work.
I guess my gripe is about proposing a solution and not willing to
extend it in light of people providing issues with it. Last time I
check we don't put things into the kernel w/o any review and if
people have issues that are reasonable they get hashed out. It seems
that the onus is on the initial submitter to either show that what
they are providing is sufficient and w/o issue or incorporate the
feedback.
More specifically, we have a way to specify what devices are connect
on I2C today. I'm not convinced there is any value in creating yet
another mechanism, especially in an interface that in theory should
be linux agnostic.
- k
next prev parent reply other threads:[~2007-05-18 16:26 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 14:38 [PATCH 3/5] powerpc: Document device nodes for I2C devices Scott Wood
2007-05-17 16:12 ` Kumar Gala
2007-05-17 16:17 ` Scott Wood
2007-05-17 16:39 ` Kumar Gala
2007-05-17 16:47 ` Scott Wood
2007-05-17 17:21 ` Kumar Gala
2007-05-17 18:29 ` Scott Wood
2007-05-18 15:15 ` [i2c] " Jean Delvare
2007-05-18 16:24 ` Kumar Gala [this message]
2007-05-18 16:35 ` Scott Wood
2007-05-18 17:10 ` Kumar Gala
2007-05-18 17:17 ` Scott Wood
2007-05-18 17:33 ` Kumar Gala
2007-05-18 17:55 ` Scott Wood
2007-05-20 11:53 ` Jean Delvare
2007-05-21 14:57 ` Scott Wood
2007-05-19 0:04 ` Matt Sealey
2007-05-19 0:17 ` Segher Boessenkool
2007-05-19 13:41 ` Matt Sealey
2007-05-19 16:25 ` Segher Boessenkool
2007-05-20 14:53 ` Matt Sealey
2007-05-20 15:48 ` Segher Boessenkool
2007-05-27 9:48 ` Matt Sealey
2007-05-20 11:42 ` Jean Delvare
2007-05-18 20:07 ` Segher Boessenkool
2007-05-17 19:18 ` Segher Boessenkool
2007-05-17 19:32 ` Scott Wood
2007-05-17 19:44 ` Segher Boessenkool
2007-05-17 21:15 ` Scott Wood
2007-05-18 15:27 ` [i2c] " Jean Delvare
2007-05-18 15:58 ` Scott Wood
2007-05-18 16:29 ` Kumar Gala
2007-05-18 16:31 ` Jean Delvare
2007-05-18 16:56 ` Kumar Gala
2007-05-18 19:00 ` David Brownell
2007-05-18 15:19 ` 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=D50C4D36-CEA5-4F7F-8A4C-CC747DF85865@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=i2c@lm-sensors.org \
--cc=khali@linux-fr.org \
--cc=linuxppc-dev@ozlabs.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).