From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: Evan McClain <aeroevan@gmail.com>
Cc: linux-leds@vger.kernel.org
Subject: Re: Chromebook Keyboard LEDs
Date: Mon, 04 Jan 2016 10:24:15 +0100 [thread overview]
Message-ID: <568A3A3F.6030700@samsung.com> (raw)
In-Reply-To: <1451771642.25561.10.camel@gmail.com>
Hi Evan,
Please submit the driver officially, according to the rules
stated in the Documentation/SubmittingPatches, so that we could
discuss it. You'll also need to add your Signed-off-by tag.
On 01/02/2016 10:54 PM, Evan McClain wrote:
> Hi list,
>
> I'm not sure how kosher it is to submit changes that I didn't author
> (cherry-picks from the chromium kernel), but since these patches are a
> few years old and having support in the mainline kernel would be nice I
> thought I'd give it a shot.
>
> I have tested on my Chromebook Pixel 2 (samus) which runs fine but is
> missing a few drivers (this and ASoC, but ASoC isn't as easy).
>
>
> The following changes since commit
> 376886d44f4cba72c4942aa1ac834ba00f6f222d:
>
> leds: bcm6358: remove unneeded busy status check (2015-12-17 09:39:02
> +0100)
>
> are available in the git repository at:
>
> https://github.com/aeroevan/linux.git for-leds
>
> for you to fetch changes up to
> 589e241e11fa01a5fef59b40c9ad826e11322e4f:
>
> leds-chromeos-keyboard: Add ACPI _HID probing (2016-01-01 02:04:09
> -0500)
>
> ----------------------------------------------------------------
> Duncan Laurie (1):
> leds-chromeos-keyboard: Add ACPI _HID probing
>
> Simon Que (3):
> leds: Add Chrome OS keyboard LEDs driver
> leds: chromeos keyboard name should contain "kbd_backlight"
> leds: Fix chromeos keyboard LED suspend behavior
>
> drivers/leds/Kconfig | 7 ++
> drivers/leds/Makefile | 1 +
> drivers/leds/leds-chromeos-keyboard.c | 127
> ++++++++++++++++++++++++++++++++++
> 3 files changed, 135 insertions(+)
> create mode 100644 drivers/leds/leds-chromeos-keyboard.c
>
> Thanks
>
--
Best Regards,
Jacek Anaszewski
prev parent reply other threads:[~2016-01-04 9:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-02 21:54 Chromebook Keyboard LEDs Evan McClain
2016-01-04 9:24 ` Jacek Anaszewski [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=568A3A3F.6030700@samsung.com \
--to=j.anaszewski@samsung.com \
--cc=aeroevan@gmail.com \
--cc=linux-leds@vger.kernel.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.