devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: cooloney@gmail.com, rpurdie@rpsys.net,
	linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
	Matthew.Fatheree@belkin.com
Subject: Re: [PATCH RESEND v6 0/2] Driver for TI tlc591xx 8/16 Channel i2c LED driver
Date: Mon, 17 Aug 2015 16:21:47 +0200	[thread overview]
Message-ID: <20150817142147.GG7537@lunn.ch> (raw)
In-Reply-To: <55D1EBA8.9090609@ti.com>

> > Hi Tomi
> > 
> > Our discussions were going around in circles, no progress being made.
> > The subsystem maintainer is ultimately the one who needs to decide,
> > bar Linus himself. Bryan Wu has seen all the discussions, and
> > ultimately decided the driver was O.K, despite any unresolved issues
> > you might have.
> 
> If so, Bryan did not comment to the unanswered questions in any way.
> More probable is that he missed them.

I would not jump to that conclusion. As one of the maintainers of
Marvell SoCs, i don't feel the need to address every open question
going back and forward between two developers, when i decide to end
the discussion by just accepting the patch.

> > If you think your PWM code is so much better, please submit a revert
> > patch plus your PWM LED driver. We can find somebody to do a side by
> > side review.
> 
> It's not about the driver code. That can be cleaned up if needed. The
> question is whether the driver should be a PWM driver or a LED driver.

There i disagree. It is all about the code. Release early, release
often.  Show us the code. Get it discussed, reviewed, tested, and then
ultimately merged.

You keep saying PWM is the way to solve this problem, but where is
your code showing your solution is superior to mine, yet still solves
my use case?

So please stop talking and show us the code.

   Thanks
	Andrew

  reply	other threads:[~2015-08-17 14:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-17 22:08 [PATCH RESEND v6 0/2] Driver for TI tlc591xx 8/16 Channel i2c LED driver Andrew Lunn
2015-03-17 22:08 ` [PATCH RESEND v6 1/2] leds: tlc591xx: Document binding for the TI " Andrew Lunn
2015-04-20 13:09   ` Jacek Anaszewski
2015-04-20 17:46     ` Bryan Wu
2015-03-17 22:08 ` [PATCH RESEND v6 2/2] leds: tlc591xx: Driver " Andrew Lunn
2015-04-20  9:06   ` Jacek Anaszewski
2015-04-20 11:59     ` Andrew Lunn
2015-04-20 13:07       ` Jacek Anaszewski
     [not found]         ` <5534FA13.9090502-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-04-20 17:49           ` Bryan Wu
2015-03-29 19:28 ` [PATCH RESEND v6 0/2] Driver for TI tlc591xx " Andrew Lunn
2015-03-30 22:10   ` Bryan Wu
2015-08-17 12:11 ` Tomi Valkeinen
2015-08-17 13:27   ` Andrew Lunn
2015-08-17 14:11     ` Tomi Valkeinen
2015-08-17 14:21       ` Andrew Lunn [this message]
2015-08-17 16:40         ` Tomi Valkeinen
2015-08-17 16:48           ` Andrew Lunn
2015-08-17 17:08             ` Bryan Wu
2015-08-17 20:47             ` Tomi Valkeinen

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=20150817142147.GG7537@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=Matthew.Fatheree@belkin.com \
    --cc=cooloney@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=rpurdie@rpsys.net \
    --cc=tomi.valkeinen@ti.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 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).