From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Linux LED Subsystem <linux-leds@vger.kernel.org>,
Brian Norris <computersforpeace@gmail.com>,
Jacek Anaszewski <j.anaszewski@samsung.com>
Subject: Re: [PATCH 2/2] leds: trigger: Introduce a MTD (NAND/NOR) trigger
Date: Tue, 12 Apr 2016 21:46:47 +0200 [thread overview]
Message-ID: <20160412214647.1249e587@bbrezillon> (raw)
In-Reply-To: <CAAEAJfA38ykPJb4yvs75ZqkQNkDJm4OrvW=f=wq2KZ7P9nh-PQ@mail.gmail.com>
On Tue, 12 Apr 2016 16:35:43 -0300
Ezequiel Garcia <ezequiel@vanguardiasur.com.ar> wrote:
> On 12 April 2016 at 15:40, Ezequiel Garcia
> <ezequiel@vanguardiasur.com.ar> wrote:
> > On 12 April 2016 at 15:27, Boris Brezillon
> > <boris.brezillon@free-electrons.com> wrote:
> >> Hi Ezequiel,
> >>
> >> On Tue, 12 Apr 2016 13:26:35 -0300
> >> Ezequiel Garcia <ezequiel@vanguardiasur.com.ar> wrote:
> >>
> >>> This commit introduces a MTD trigger for flash (NAND/NOR) device
> >>> activity. The implementation is copied from IDE disk.
> >>>
> >>> This deprecates the "nand-disk" LED trigger, but for backwards
> >>> compatibility, we still keep the "nand-disk" trigger around.
> >>>
> >>> The motivation for deprecating the "nand-disk" LED trigger is that
> >>> it only works for NAND drivers, whereas the "mtd" LED trigger
> >>> is more generic (in fact, "nand-disk" currently only works for
> >>> certain NAND drivers).
> >>>
> >>> Signed-off-by: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
> >>> ---
> >>> drivers/leds/trigger/Kconfig | 8 +++++++
> >>> drivers/leds/trigger/Makefile | 1 +
> >>> drivers/leds/trigger/ledtrig-mtd.c | 49 ++++++++++++++++++++++++++++++++++++++
> >>> drivers/mtd/mtdcore.c | 7 ++++++
> >>> drivers/mtd/nand/nand_base.c | 29 +---------------------
> >>> include/linux/leds.h | 6 +++++
> >>
> >> I'd suggest splitting this patch in 2, one adding ledtrig-mtd code, and
> >> another one make use of ledtrig_mtd_activity() and removing
> >> nand-trigger code.
> >>
> >
> > Sure, that sounds good.
> >
>
> One comment about the above: notice that if we split in two patches
> as you suggest, we would create a dependency between patches.
>
> I don't have any problem doing this, but it sounds like it might make
> maintainers
> life harder.
I guess both patches will go through the same tree even if they are
split (either leds or mtd), so that's not really a problem.
Note that you have the same dependency problem with the single patch
approach (if another leds or mtd patch is touching one of the file
modified here, we may have a merge conflict).
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2016-04-12 19:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 16:26 [PATCH 0/2] LED trigger on MTD activity Ezequiel Garcia
2016-04-12 16:26 ` [PATCH 1/2] mtd: Uninline mtd_write_oob and move it to mtdcore.c Ezequiel Garcia
2016-04-12 18:15 ` Boris Brezillon
2016-04-12 18:35 ` Ezequiel Garcia
2016-04-12 16:26 ` [PATCH 2/2] leds: trigger: Introduce a MTD (NAND/NOR) trigger Ezequiel Garcia
2016-04-12 18:27 ` Boris Brezillon
2016-04-12 18:40 ` Ezequiel Garcia
2016-04-12 19:11 ` Boris Brezillon
2016-04-12 19:35 ` Ezequiel Garcia
2016-04-12 19:46 ` Boris Brezillon [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=20160412214647.1249e587@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 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).