From: Greg KH <greg@kroah.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
ak@suse.de, len.brown@intel.com, linux-ide@vger.kernel.org,
dz@debian.org, minyard@acm.org, j.w.r.degoede@hhs.nl,
lm-sensors@lm-sensors.org, rlove@rlove.org, bzolnier@gmail.com,
dmitry.torokhov@gmail.com, mzxreary@0pointer.de,
stelian@popies.net, ibm-acpi@hmh.eng.br, ambx1@neo.rr.com,
gimli@dark-green.com
Subject: Re: [PATCH] drivers/firmware: const-ify DMI API and internals
Date: Sun, 9 Sep 2007 10:51:42 -0700 [thread overview]
Message-ID: <20070909175142.GB32447@kroah.com> (raw)
In-Reply-To: <46D98CD0.9040206@garzik.org>
On Sat, Sep 01, 2007 at 12:01:20PM -0400, Jeff Garzik wrote:
> Greg KH wrote:
>> On Sat, Sep 01, 2007 at 10:27:19AM -0400, Jeff Garzik wrote:
>>> commit 457b6eb3bf3341d2e143518a0bb99ffbb8d754c4
>>> Author: Jeff Garzik <jeff@garzik.org>
>>> Date: Sat Sep 1 10:16:45 2007 -0400
>>>
>>> drivers/firmware: const-ify DMI API and internals
>>> Three main sets of changes:
>>> 1) dmi_get_system_info() return value should have been marked
>>> const,
>>> since callers should not be changing that data.
>>> 2) const-ify DMI internals, since DMI firmware tables should,
>>> whenever possible, be marked const to ensure we never ever write
>>> to
>>> that data area.
>>> 3) const-ify DMI API, to enable marking tables const where
>>> possible
>>> in low-level drivers.
>>> And if we're really lucky, this might enable some additional
>>> optimizations on the part of the compiler.
>>> The bulk of the changes are #2 and #3, which are interrelated.
>>> #1 could
>>> have been a separate patch, but it was so small compared to the
>>> others,
>>> it was easier to roll it into this changeset.
>> Looks great to me, do you want me to take this through my driver tree?
>> I'd be glad to do so.
>
> I was just going to push it myself, but have no strong feelings on the
> matter.
Ok, you can push it, that's fine with me. Feel free to add my:
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
if you want.
thanks,
greg k-h
next prev parent reply other threads:[~2007-09-09 17:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-01 14:27 [PATCH] drivers/firmware: const-ify DMI API and internals Jeff Garzik
2007-09-01 15:36 ` Greg KH
2007-09-01 16:01 ` Jeff Garzik
2007-09-09 17:51 ` Greg KH [this message]
2007-09-09 20:24 ` Sam Ravnborg
2007-09-09 21:12 ` Greg KH
2007-09-01 16:33 ` Andi Kleen
2007-09-01 21:21 ` Satyam Sharma
2007-09-02 17:17 ` [lm-sensors] " Jean Delvare
2007-09-11 21:54 ` Bartlomiej Zolnierkiewicz
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=20070909175142.GB32447@kroah.com \
--to=greg@kroah.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=ambx1@neo.rr.com \
--cc=bzolnier@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=dz@debian.org \
--cc=gimli@dark-green.com \
--cc=ibm-acpi@hmh.eng.br \
--cc=j.w.r.degoede@hhs.nl \
--cc=jeff@garzik.org \
--cc=len.brown@intel.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=minyard@acm.org \
--cc=mzxreary@0pointer.de \
--cc=rlove@rlove.org \
--cc=stelian@popies.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).