From: J Witteveen <jwitteve@liacs.nl>
To: mjg@redhat.com
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Platform: add Samsung Laptop platform driver
Date: Sun, 26 Jun 2011 17:08:55 +0200 [thread overview]
Message-ID: <20110626150855.GA19359@liacs.nl> (raw)
On Fri, Feb 11, 2011 at 10:17, Jouke Witteveen <j.witteveen@gmail.com> wrote:
> On Wed, Feb 9, 2011 at 23:40, Greg KH <greg@kroah.com> wrote:
>> From: Greg Kroah-Hartman <gregkh@suse.de>
>>
>> This adds the samsung-laptop driver to the kernel. It now supports
>> all known Samsung laptops.
>>
>
> I don't see the N510, is this intentional? The netbook does not differ
> that much from some that are included.
>
The N510 benefits from this code as well. Below is a patch to include support.
Signed-off-by: Jouke Witteveen <j.witteveen@gmail.com>
Thanks,
- Jouke
--- a/drivers/platform/x86/samsung-laptop.c 2011-06-26 16:18:06.517840468 +0200
+++ b/drivers/platform/x86/samsung-laptop.c 2011-06-26 16:19:14.677574644 +0200
@@ -521,6 +521,16 @@ static struct dmi_system_id __initdata s
.callback = dmi_check_cb,
},
{
+ .ident = "N510",
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR,
+ "SAMSUNG ELECTRONICS CO., LTD."),
+ DMI_MATCH(DMI_PRODUCT_NAME, "N510"),
+ DMI_MATCH(DMI_BOARD_NAME, "N510"),
+ },
+ .callback = dmi_check_cb,
+ },
+ {
.ident = "X125",
.matches = {
DMI_MATCH(DMI_SYS_VENDOR,
next reply other threads:[~2011-06-26 15:08 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-26 15:08 J Witteveen [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-11 17:57 [PATCH] Platform: add Samsung Laptop platform driver Tommaso Massimi
2011-03-05 4:24 Greg KH
2011-03-05 4:24 ` Greg KH
2011-03-11 17:43 ` Matthew Garrett
2011-03-11 19:35 ` Greg KH
2011-03-11 19:44 ` Matthew Garrett
2011-03-11 19:52 ` Greg KH
2011-03-11 19:55 ` Matthew Garrett
2011-03-14 15:18 ` Jörg-Volker Peetz
2011-02-27 15:36 Greg KH
2011-02-25 22:47 Greg KH
2011-02-09 22:40 Greg KH
2011-02-09 22:44 ` Randy Dunlap
2011-02-09 22:50 ` Greg KH
2011-02-09 22:58 ` Matthew Garrett
2011-02-09 22:50 ` Matthew Garrett
2011-02-09 23:02 ` Greg KH
2011-02-11 9:17 ` Jouke Witteveen
2011-02-11 11:37 ` Richard Schütz
2011-02-11 15:22 ` Greg KH
2011-02-11 16:27 ` Richard Schütz
2011-02-25 21:01 ` Greg KH
2011-02-11 15:45 ` Matthew Garrett
2011-02-11 18:42 ` Greg KH
2011-02-16 10:06 ` Nikolai Kondrashov
2011-02-25 21:03 ` Greg KH
2011-02-25 21:49 ` Nikolai Kondrashov
2011-02-25 22:50 ` Greg KH
2011-03-10 7:00 ` Nikolai Kondrashov
2011-03-10 17:01 ` Greg KH
2011-03-10 17:13 ` Nikolai Kondrashov
2011-03-10 17:19 ` Greg KH
2011-03-10 17:28 ` Nikolai Kondrashov
2011-03-10 18:09 ` Greg KH
2011-03-10 21:05 ` Nikolai Kondrashov
2011-03-10 21:15 ` Greg KH
2011-03-11 7:12 ` Nikolai Kondrashov
2011-03-11 17:03 ` Greg KH
2011-03-11 19:07 ` Nikolai Kondrashov
2011-03-11 19:34 ` Greg KH
2011-03-11 20:20 ` Nikolai Kondrashov
2011-03-11 20:23 ` Nikolai Kondrashov
2011-03-11 20:35 ` Greg KH
2011-03-11 20:30 ` Greg KH
2011-03-13 10:03 ` Nikolai Kondrashov
2011-03-13 10:55 ` Richard Schütz
2011-03-13 13:02 ` Nikolai Kondrashov
2011-03-13 16:18 ` Greg KH
2011-03-13 17:49 ` Nikolai Kondrashov
2011-03-13 17:58 ` Greg KH
2011-03-13 16:17 ` Greg KH
2011-03-13 16:28 ` Matthew Garrett
2011-03-13 17:51 ` Nikolai Kondrashov
2011-03-13 17:50 ` Nikolai Kondrashov
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=20110626150855.GA19359@liacs.nl \
--to=jwitteve@liacs.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=platform-driver-x86@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.