From: Christoph Hellwig <hch@infradead.org>
To: Len Brown <len.brown@intel.com>
Cc: Adrian Bunk <bunk@stusta.de>,
Alexey Y Starikovskiy <alexey.y.starikovskiy@intel.com>,
Robert Moore <robert.moore@intel.com>,
linux-kernel@vger.kernel.org,
ACPI Developers <acpi-devel@lists.sourceforge.net>
Subject: Re: [RFC: 2.6 patch] drivers/acpi/: possible cleanups
Date: Sun, 30 Jan 2005 17:39:29 +0000 [thread overview]
Message-ID: <20050130173929.GA32014@infradead.org> (raw)
In-Reply-To: <1106867060.2400.2297.camel@d845pe>
On Thu, Jan 27, 2005 at 06:04:20PM -0500, Len Brown wrote:
> I've already asked Bob Moore to migrate to the use of static in the
> interpreter. There are some somewhat urgent functional issues he needs
> to focus on first, but static is on the list. If we allow him to do it
> upstream (w/o looking at your patch), then we can avoid a fork in the
> core interpreter code.
>
> At the same time, the non "R. Byron Moore" files, such as those in
> drivers/acpi, but not in the lower sub-directories, are straight GPL and
> I'll be happy to accept patches to those files immediately. Note that
> there are 4 straight GPL files in include/acpi as well -- so like the
> drivers/acpi/* files, we can modify them any time when cleanups are
> appropriate in the Linux release cycle.
The files are licensed under a BSD license so all patches against it
are aswell unless explicitly marked.
prev parent reply other threads:[~2005-01-30 17:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 11:01 [RFC: 2.6 patch] drivers/acpi/: possible cleanups Adrian Bunk
2005-01-27 23:04 ` Len Brown
2005-01-27 23:30 ` Dmitry Torokhov
2005-01-30 17:32 ` [2.6 patch] drivers/acpi/: make some code static Adrian Bunk
2005-01-30 17:39 ` Christoph Hellwig [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=20050130173929.GA32014@infradead.org \
--to=hch@infradead.org \
--cc=acpi-devel@lists.sourceforge.net \
--cc=alexey.y.starikovskiy@intel.com \
--cc=bunk@stusta.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.moore@intel.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 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.