From: Greg KH <greg@kroah.com>
To: Mike Waychison <mikew@google.com>
Cc: Olof Johansson <olofj@chromium.org>,
Andi Kleen <andi@firstfloor.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Robert Lippert <rlippert@google.com>,
Jon Mayer <jonmayer@google.com>,
Duncan Laurie <dlaurie@google.com>,
Aaron Durbin <adurbin@google.com>,
linux-kernel@vger.kernel.org, Tim Hockin <thockin@google.com>,
David Hendrix <dhendrix@chromium.org>,
linux-api@vger.kernel.org
Subject: Re: [PATCH v1 2/5] firmware: Basic dmi-sysfs support
Date: Thu, 17 Feb 2011 13:56:08 -0800 [thread overview]
Message-ID: <20110217215608.GA2451@kroah.com> (raw)
In-Reply-To: <20110217212805.3967.47547.stgit@mike.mtv.corp.google.com>
Overall, this looks great, just a few minor comments below:
On Thu, Feb 17, 2011 at 01:28:05PM -0800, Mike Waychison wrote:
> +config DMI_SYSFS
> + tristate "DMI table support in sysfs"
> + depends on SYSFS && DMI
> + default X86
Huh? Default should be 'N' for any new feature, unless it keeps your
machine from booting.
I think you want this option to depend on X86 though, right?
> + help
> + Say Y or M here to enable the exporting of the raw DMI table
> + data via sysfs. This is useful for consuming the data without
> + requiring any access to /dev/mem at all. Tables are found
> + under /sys/firmware/dmi when this option is enabled and
> + loaded.
I just realized (due to other work I'm doing on a laptop) that we have a
bunch of entries today in /sys/class/dmi/id which is a pointer to the
dmi "device".
Now I think this really is different (these are the raw DMI tables), but
this doesn't have anything to do with that code, right?
> + *
> + * Copyright 2010 Google, Inc.
It's 2011 :)
> +static int __init dmi_sysfs_init(void)
> +{
> + int error = -ENOMEM;
> + int val;
> +
> + /* Set up our directory */
> + dmi_kobj = kobject_create_and_add("dmi", firmware_kobj);
> + if (!dmi_kobj)
> + goto err;
> +
> + dmi_kset = kset_create_and_add("entries", NULL, dmi_kobj);
> + if (!dmi_kset)
> + goto err;
> +
> + val = 0;
> + error = dmi_walk(dmi_sysfs_register_handle, &val);
> + if (error)
> + goto err;
> + if (val) {
> + error = val;
> + goto err;
> + }
> +
> + pr_info("dmi-sysfs: loaded.\n");
Is this really needed? pr_dbg() instead please?
> +
> + return 0;
> +err:
> + cleanup_entry_list();
> + kset_unregister(dmi_kset);
> + kobject_put(dmi_kobj);
> + return error;
> +}
> +
> +/* clean up everything. */
> +static void __exit dmi_sysfs_exit(void)
> +{
> + pr_info("dmi-sysfs: unloading.\n");
> + cleanup_entry_list();
> + kset_unregister(dmi_kset);
> + kobject_put(dmi_kobj);
> +}
> +
> +module_init(dmi_sysfs_init);
> +module_exit(dmi_sysfs_exit);
> +
> +MODULE_AUTHOR("Google, Inc.");
You don't want your name here?
thanks,
greg k-h
next prev parent reply other threads:[~2011-02-17 21:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 21:27 [PATCH v1 0/5] Exporting DMI entries via syfs Mike Waychison
[not found] ` <20110217212754.3967.98648.stgit-tzAwxxnF6Tt6FDdRrpk8kO4/NqBCd+6Q@public.gmane.org>
2011-02-17 21:28 ` [PATCH v1 1/5] firmware: Add DMI entry types to the headers Mike Waychison
2011-02-17 21:28 ` [PATCH v1 2/5] firmware: Basic dmi-sysfs support Mike Waychison
2011-02-17 21:56 ` Greg KH [this message]
[not found] ` <20110217215608.GA2451-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2011-02-22 23:31 ` Mike Waychison
[not found] ` <4D644736.9050109-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2011-02-23 0:07 ` Luck, Tony
[not found] ` <20110217212805.3967.47547.stgit-tzAwxxnF6Tt6FDdRrpk8kO4/NqBCd+6Q@public.gmane.org>
2011-02-17 21:42 ` Tim Hockin
2011-02-22 23:49 ` Rob Lippert
[not found] ` <AANLkTi=wpVRSxY0HTnnJEeEN-VEOBQ7XJM5TrUu9Chqd-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-02-22 23:58 ` Mike Waychison
2011-02-17 21:28 ` [PATCH v1 3/5] firmware: Break out system_event_log in dmi-sysfs Mike Waychison
2011-02-17 21:28 ` [PATCH v1 4/5] firmware: Expose DMI type 15 System Event Log Mike Waychison
2011-02-17 21:28 ` [PATCH v1 5/5] firmware: Add documentation for /sys/firmware/dmi Mike Waychison
[not found] ` <20110217212821.3967.22439.stgit-tzAwxxnF6Tt6FDdRrpk8kO4/NqBCd+6Q@public.gmane.org>
2011-02-17 21:50 ` Tim Hockin
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=20110217215608.GA2451@kroah.com \
--to=greg@kroah.com \
--cc=adurbin@google.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andi@firstfloor.org \
--cc=dhendrix@chromium.org \
--cc=dlaurie@google.com \
--cc=jonmayer@google.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikew@google.com \
--cc=olofj@chromium.org \
--cc=rlippert@google.com \
--cc=thockin@google.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;
as well as URLs for NNTP newsgroup(s).