mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Hubert Feurstein <h.feurstein@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 1/4] led: unify led trigger tables
Date: Wed, 11 Dec 2019 09:39:05 +0100	[thread overview]
Message-ID: <20191211083905.k4pzx6ckm2paokzs@pengutronix.de> (raw)
In-Reply-To: <20191210171305.24276-1-h.feurstein@gmail.com>

On Tue, Dec 10, 2019 at 06:13:01PM +0100, Hubert Feurstein wrote:
> Currently we have two slightly different led-trigger tables. One in the
> core module, and the other one in the led-triggers module. The one in the
> core module, which is used to parse the device-tree triggers, is lacking
> net-rx and net-tx.
> 
> Signed-off-by: Hubert Feurstein <h.feurstein@gmail.com>
> ---
>  drivers/led/core.c         | 46 +++++++++++++++++++++++---------------
>  drivers/led/led-triggers.c | 25 ---------------------
>  2 files changed, 28 insertions(+), 43 deletions(-)

Applied, thanks

Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      parent reply	other threads:[~2019-12-11  8:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-10 17:13 Hubert Feurstein
2019-12-10 17:13 ` [PATCH 2/4] led: add documentation for net-tx and net-rx triggers Hubert Feurstein
2019-12-10 17:13 ` [PATCH 3/4] led: check for 'barebox, default-trigger' when 'linux, default-trigger' is not found Hubert Feurstein
2019-12-10 17:13 ` [PATCH 4/4] led: parse panic-indicator from device-tree Hubert Feurstein
2019-12-11  8:39 ` Sascha Hauer [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=20191211083905.k4pzx6ckm2paokzs@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=h.feurstein@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox