From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Jacek Anaszewski <j.anaszewski@samsung.com>
Cc: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
linux-mtd@lists.infradead.org, linux-leds@vger.kernel.org,
Brian Norris <computersforpeace@gmail.com>
Subject: Re: [PATCH v2 0/4] LED trigger on MTD activity
Date: Wed, 13 Apr 2016 20:39:05 +0200 [thread overview]
Message-ID: <20160413203905.06371b4c@bbrezillon> (raw)
In-Reply-To: <570E0506.4040705@samsung.com>
Hi Jacek,
On Wed, 13 Apr 2016 10:36:22 +0200
Jacek Anaszewski <j.anaszewski@samsung.com> wrote:
> Hi Ezequiel,
>
> Thanks for the update. From the previous discussion I've inferred
> that it has been agreed on the whole patch to go through the LED tree.
>
> Applied whole patch set to the for-next branch of linux-leds.git,
> with acks from Boris, then.
Can you provide an immutable branch containing those changes?
Thanks,
Boris
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-04-13 18:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 20:46 [PATCH v2 0/4] LED trigger on MTD activity Ezequiel Garcia
2016-04-12 20:46 ` Ezequiel Garcia
2016-04-12 20:46 ` [PATCH v2 1/4] mtd: Uninline mtd_write_oob and move it to mtdcore.c Ezequiel Garcia
2016-04-12 20:46 ` Ezequiel Garcia
2016-04-12 20:46 ` [PATCH v2 2/4] leds: trigger: Introduce a MTD (NAND/NOR) trigger Ezequiel Garcia
2016-04-12 20:46 ` Ezequiel Garcia
2016-04-12 20:46 ` [PATCH v2 3/4] mtd: nand: Remove the "nand-disk" LED trigger Ezequiel Garcia
2016-04-12 20:46 ` Ezequiel Garcia
2016-04-12 20:46 ` [PATCH v2 4/4] mtd: Hook I/O activity to the MTD " Ezequiel Garcia
2016-04-12 20:46 ` Ezequiel Garcia
2016-04-12 20:58 ` [PATCH v2 0/4] LED trigger on MTD activity Boris Brezillon
2016-04-12 20:58 ` Boris Brezillon
2016-04-13 8:36 ` Jacek Anaszewski
2016-04-13 18:39 ` Boris Brezillon [this message]
2016-04-14 7:45 ` Jacek Anaszewski
2016-04-14 10:03 ` Boris Brezillon
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=20160413203905.06371b4c@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=j.anaszewski@samsung.com \
--cc=linux-leds@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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.