All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: Vincent Donnefort <vdonnefort@gmail.com>
Cc: linux-leds@vger.kernel.org, simon.guinot@sequanux.org,
	Sakari Ailus <sakari.ailus@linux.intel.com>
Subject: Re: Workqueue core implementation
Date: Fri, 30 Oct 2015 08:55:23 +0100	[thread overview]
Message-ID: <5633226B.1030009@samsung.com> (raw)
In-Reply-To: <20151029165905.GA15462@ns3274321.ip-5-39-88.eu>

Hi Vincent,

On 10/29/2015 05:59 PM, Vincent Donnefort wrote:
> Hi Jacek,
>
> I saw on your git branch "linux-leds/devel" that you are working on a
> core solution for workqueues with the new led_set_brightness_nopm()
> function and thus you are removing workqueues from leds-* drivers.
>
> Since I'll need to add GPIO can_sleep support to a LED driver, I'm
> interested to know when are you planning to merge this work, to avoid
> to submit a patch to add workqueue which will be quickly deprecated.

I need some acks for these patches. I've already collected a few [1],
but there hasn't been any reply to the patch [2] so far, which removes
the reasons for modifications requested by Sakari in the thread [1].
Now I am waiting for his review of the patch [2] (btw it should be
version 3,1, and not 10.1 - I counted mistakenly also previous RFC
patch sets this time). Nevertheless, if I got acks, or even Tested-by
from you, it would speed up the things significantly.

Cc Sakari.

[1] https://lkml.org/lkml/2015/10/16/591
[2] http://www.spinics.net/lists/linux-leds/msg05045.html

-- 
Best Regards,
Jacek Anaszewski

      reply	other threads:[~2015-10-30  7:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-29 16:59 Workqueue core implementation Vincent Donnefort
2015-10-30  7:55 ` Jacek Anaszewski [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=5633226B.1030009@samsung.com \
    --to=j.anaszewski@samsung.com \
    --cc=linux-leds@vger.kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=simon.guinot@sequanux.org \
    --cc=vdonnefort@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.