All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-pwm@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: Is PWM subsystem maintainable?
Date: Tue, 17 Jan 2017 00:33:13 +0200	[thread overview]
Message-ID: <CAHp75Veq_kEyghXAwCv8Z6zKTA-mF0bvJnALzm-2C0-dVZs9mA@mail.gmail.com> (raw)
In-Reply-To: <20170116215851.GA18142@ulmo.ba.sec>

On Mon, Jan 16, 2017 at 11:58 PM, Thierry Reding
<thierry.reding@gmail.com> wrote:
> On Mon, Jan 16, 2017 at 04:50:45PM +0200, Andy Shevchenko wrote:
>> Hi!
>>
>> I'm really puzzled. Do we have a maintainer for PWM subsystem? Is he
>> responsive?
>
> Oh, I'm around, just having a streak of bad luck since early December
> and therefore more busy with real life than I'd like.

Good you are here!

>> We sent already two series (1 + 4) of patches regarding to two
>> different drivers and not a single patch has been commented and / or
>> applied for *months*. One more had been sent week or so ago.
>>
>> For our uncountable pings we didn't receive any word on what's going on.
>> If there is any trouble with patches we would really eager to fix them.
>
> I'm aware of your patches and I plan on applying them for v4.11, I just
> need to find a large enough slot to apply, test build and push.

Thanks! It's indeed important to us.

-- 
With Best Regards,
Andy Shevchenko

      reply	other threads:[~2017-01-16 22:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-16 14:50 Is PWM subsystem maintainable? Andy Shevchenko
2017-01-16 21:58 ` Thierry Reding
2017-01-16 22:33   ` Andy Shevchenko [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=CAHp75Veq_kEyghXAwCv8Z6zKTA-mF0bvJnALzm-2C0-dVZs9mA@mail.gmail.com \
    --to=andy.shevchenko@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=thierry.reding@gmail.com \
    --cc=torvalds@linux-foundation.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 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.