From: Prarit Bhargava <prarit@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, dzickus@redhat.com,
Greg KH <gregkh@suse.de>
Subject: Re: [PATCH]: SMBIOS: Add initial code and export version via sysfs
Date: Thu, 17 Mar 2011 15:12:50 -0400 [thread overview]
Message-ID: <4D825D32.1080309@redhat.com> (raw)
In-Reply-To: <20110317190932.074949b4@lxorguk.ukuu.org.uk>
On 03/17/2011 03:09 PM, Alan Cox wrote:
>> +static struct class smbios_class = {
>> + .name = "smbios",
>> + .dev_release = (void(*)(struct device *)) kfree,
>> +};
>>
> I thought the policy was no new classes- Greg ?
>
Greg, eventually the SMBIOS code could replace the mixed DMI/SMBIOS code
we have right now. If there is a "no new classes" policy, could you
give me an idea of what I should do/use instead? The DMI stuff is
currently in its own class ...
>
>> + smbios_iounmap(buf, sizeof(*smbios_step));
>> + printk(KERN_INFO "SMBIOS: Invalid STEP table checksum = %u\n",
>> + chksum1);
>>
> Surely this isn't INFO ?
>
>
Good point :) I can certainly make that higher or a WARN_ON in the next
version.
P.
next prev parent reply other threads:[~2011-03-17 19:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 13:57 [PATCH]: SMBIOS: Add initial code and export version via sysfs Prarit Bhargava
2011-03-17 19:09 ` Alan Cox
2011-03-17 19:12 ` Prarit Bhargava [this message]
2011-03-17 19:22 ` Greg KH
2011-03-17 19:30 ` Greg KH
2011-03-17 19:55 ` Prarit Bhargava
2011-03-17 20:07 ` Greg KH
2011-03-21 15:45 ` Prarit Bhargava
2011-03-21 16:06 ` Alan Cox
2011-03-27 22:29 ` Prarit Bhargava
2011-03-17 20:08 ` Prarit Bhargava
2011-03-17 20:15 ` Greg KH
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=4D825D32.1080309@redhat.com \
--to=prarit@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dzickus@redhat.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@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.