linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Cc: linux-mtd@lists.infradead.org, linux-leds@vger.kernel.org,
	Brian Norris <computersforpeace@gmail.com>,
	Boris Brezillon <boris.brezillon@free-electrons.com>
Subject: Re: [PATCH v2 0/4] LED trigger on MTD activity
Date: Wed, 13 Apr 2016 10:36:22 +0200	[thread overview]
Message-ID: <570E0506.4040705@samsung.com> (raw)
In-Reply-To: <1460494002-8578-1-git-send-email-ezequiel@vanguardiasur.com.ar>

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.

Thanks,
Jacek Anaszewski

On 04/12/2016 10:46 PM, Ezequiel Garcia wrote:
> After our recent discussion [1], here's a proper patchset.
>
> The first patch is a minor cleanup which moves mtd_write_oob
> out of mtd.h header.
>
> The second patch introduces the LED MTD trigger.
>
> The third patch removes the "nand-disk" LED trigger
> from the NAND core.
>
> The fourth patch completes the series by calling ledtrig_mtd_activity
> on all MTD I/O activity paths.
>
> Changes from v1:
>
>    * Split the patches, suggested by Boris.
>
> Feedback is welcome!
>
> [1] http://www.spinics.net/lists/linux-leds/msg05906.html
>
> Ezequiel Garcia (4):
>    mtd: Uninline mtd_write_oob and move it to mtdcore.c
>    leds: trigger: Introduce a MTD (NAND/NOR) trigger
>    mtd: nand: Remove the "nand-disk" LED trigger
>    mtd: Hook I/O activity to the MTD LED trigger
>
>   drivers/leds/trigger/Kconfig       |  8 +++++++
>   drivers/leds/trigger/Makefile      |  1 +
>   drivers/leds/trigger/ledtrig-mtd.c | 45 ++++++++++++++++++++++++++++++++++++++
>   drivers/mtd/mtdcore.c              | 19 ++++++++++++++++
>   drivers/mtd/nand/nand_base.c       | 29 +-----------------------
>   include/linux/leds.h               |  6 +++++
>   include/linux/mtd/mtd.h            | 12 +---------
>   7 files changed, 81 insertions(+), 39 deletions(-)
>   create mode 100644 drivers/leds/trigger/ledtrig-mtd.c
>

  parent reply	other threads:[~2016-04-13  8:36 UTC|newest]

Thread overview: 10+ 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 ` [PATCH v2 1/4] mtd: Uninline mtd_write_oob and move it to mtdcore.c 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 ` [PATCH v2 3/4] mtd: nand: Remove the "nand-disk" LED trigger 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:58 ` [PATCH v2 0/4] LED trigger on MTD activity Boris Brezillon
2016-04-13  8:36 ` Jacek Anaszewski [this message]
2016-04-13 18:39   ` Boris Brezillon
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=570E0506.4040705@samsung.com \
    --to=j.anaszewski@samsung.com \
    --cc=boris.brezillon@free-electrons.com \
    --cc=computersforpeace@gmail.com \
    --cc=ezequiel@vanguardiasur.com.ar \
    --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 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).