All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: Lars Poeschel <poeschel@lemonage.de>,
	Arnd Bergmann <arnd@arndb.de>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	Ryan Mallon <rmallon@gmail.com>,
	"mcrapet@gmail.com" <mcrapet@gmail.com>
Subject: Re: [PATCH 00/14] misc/ep93xx_pwm: cleanup driver for conversion to PWM framework
Date: Thu, 30 May 2013 13:41:27 +0200	[thread overview]
Message-ID: <20130530114126.GC20194@mithrandir> (raw)
In-Reply-To: <ADE657CA350FB648AAC2C43247A983F0021DA657044E@AUSP01VMBX24.collaborationhost.net>

[-- Attachment #1: Type: text/plain, Size: 1547 bytes --]

On Wed, May 29, 2013 at 04:33:21PM -0500, H Hartley Sweeten wrote:
> On Tuesday, May 28, 2013 4:42 AM, Lars Poeschel wrote:
> > On Tuesday 28 May 2013 at 13:00:12, Thierry Reding wrote:
> >> I've added Lars Poeschel on Cc, who's done some work on a sysfs
> >> interface for the PWM subsystem already. It's undergone some review
> >> already[0] and I think he's working on a v2 now.
> >> 
> >> Thierry
> >> 
> >> [0]: http://marc.info/?l=linux-kernel&m=136499756101273&w=2
> >
> > I currently do not have the time to work on a v2 of the pwm sysfs patch but 
> > I will do it as soon as possible - if not someone else will do. 
> > Unfortunately my current involvements in other project will not allow me to 
> > do so for at least next two months.
> > I received some off-list reactions to my patches from users asking for pwm 
> > sysfs, so there is definitely a need for it!
> > If you decide to take attempt 2) (which is preferable) I recommend you to 
> > take a look at what I have done and Thierrys review comments. I took the 
> > gpiolib way and the result got rejected for very good reasons.
> 
> I just posted a PWM sysfs interface patch based on the previous work by
> Lars. Hopefully I addressed all of Thierrys review comments.

I can't find it anywhere. Maybe you used my @avionic-design.de email
address? Could you please repost using the @gmail.com address, as I have
only unreliable access to the other one ATM. And please also Cc the all
new linux-pwm@vger.kernel.org mailing list.

Thanks,
Thierry

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2013-05-30 11:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-24 23:19 [PATCH 00/14] misc/ep93xx_pwm: cleanup driver for conversion to PWM framework H Hartley Sweeten
2013-05-26 23:32 ` Ryan Mallon
2013-05-27 15:20 ` Arnd Bergmann
2013-05-27 16:27   ` H Hartley Sweeten
2013-05-27 17:12     ` Arnd Bergmann
2013-05-28 11:00       ` Thierry Reding
2013-05-28 11:42         ` Lars Poeschel
2013-05-29 21:33           ` H Hartley Sweeten
2013-05-30 11:41             ` Thierry Reding [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=20130530114126.GC20194@mithrandir \
    --to=thierry.reding@gmail.com \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=hartleys@visionengravers.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcrapet@gmail.com \
    --cc=poeschel@lemonage.de \
    --cc=rmallon@gmail.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 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.