netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Philippe Ombredanne <pombredanne@nexb.com>
Cc: Ben Whitten <ben.whitten@gmail.com>,
	rpurdie@rpsys.net, jacek.anaszewski@gmail.com,
	linux-leds@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	netdev@vger.kernel.org
Subject: Re: [PATCH v3] leds: trigger: Introduce a NETDEV trigger
Date: Fri, 8 Dec 2017 15:27:07 +0100	[thread overview]
Message-ID: <20171208142707.GA7793@amd> (raw)
In-Reply-To: <CAOFm3uGxzg45ZGmE4GRwy=oiaNERtq7tYdG4VwgZc0xgvXG6Pg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2155 bytes --]

On Thu 2017-12-07 14:01:39, Philippe Ombredanne wrote:
> Ben,
> 
> On Thu, Dec 7, 2017 at 12:46 PM, Ben Whitten <ben.whitten@gmail.com> wrote:
> > From: Ben Whitten <ben.whitten@gmail.com>
> >
> > This commit introduces a NETDEV trigger for named device
> > activity. Available triggers are link, rx, and tx.
> >
> > Signed-off-by: Ben Whitten <ben.whitten@gmail.com>
> []
> > --- /dev/null
> > +++ b/drivers/leds/trigger/ledtrig-netdev.c
> > @@ -0,0 +1,503 @@
> > +/*
> > + * LED Kernel Netdev Trigger
> > + *
> > + * Toggles the LED to reflect the link and traffic state of a named net device
> > + *
> > + * Copyright 2017 Ben Whitten <ben.whitten@gmail.com>
> > + *
> > + * Copyright 2007 Oliver Jowett <oliver@opencloud.com>
> > + *
> > + * Derived from ledtrig-timer.c which is:
> > + *  Copyright 2005-2006 Openedhand Ltd.
> > + *  Author: Richard Purdie <rpurdie@openedhand.com>
> > + *
> > + * This program is free software; you can redistribute it and/or modify
> > + * it under the terms of the GNU General Public License version 2 as
> > + * published by the Free Software Foundation.
> > + *
> > + */
> 
> Have you considered using the new SPDX id instead ? See Thomas doc
> patches and Greg and Linus comments on the topic
> Here this would likely come out this way (yes, using a C++ comment at the top):
> 
> > +// SPDX-License-Identifier: GPL-2.0
> > +/*
> > + * LED Kernel Netdev Trigger
> > + *
> > + * Toggles the LED to reflect the link and traffic state of a named net device
> > + *
> > + * Copyright 2017 Ben Whitten <ben.whitten@gmail.com>
> > + *
> > + * Copyright 2007 Oliver Jowett <oliver@opencloud.com>
> > + *
> > + * Derived from ledtrig-timer.c which is:
> > + *  Copyright 2005-2006 Openedhand Ltd.
> > + *  Author: Richard Purdie <rpurdie@openedhand.com>
> > + *
> > + */
> 
> 
> This is cleaner and simpler, don't you think?

Please consider putting SPDX where it logically belongs -- near the
copyright.

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  parent reply	other threads:[~2017-12-08 14:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-07 11:46 [PATCH v3] leds: trigger: Introduce a NETDEV trigger Ben Whitten
2017-12-07 13:01 ` Philippe Ombredanne
2017-12-07 14:19   ` Ben Whitten
2017-12-08 14:27   ` Pavel Machek [this message]
2017-12-08 14:32     ` Philippe Ombredanne

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=20171208142707.GA7793@amd \
    --to=pavel@ucw.cz \
    --cc=ben.whitten@gmail.com \
    --cc=jacek.anaszewski@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pombredanne@nexb.com \
    --cc=rpurdie@rpsys.net \
    /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).