From: Dmitry Torokhov <dtor_core@ameritech.net>
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: Thu, 27 Jan 2005 18:30:35 -0500 [thread overview]
Message-ID: <200501271830.36444.dtor_core@ameritech.net> (raw)
In-Reply-To: <1106867060.2400.2297.camel@d845pe>
On Thursday 27 January 2005 18:04, Len Brown wrote:
> Thanks for the patch Adrian.
>
> I agree that this is the right direction to go -- enforcing APIs with
> the use of static reduces the possibility of programming errors --
> particularly with many cooks in the kitchen. Indeed, just on Monday we
> discussed a patch from Alexey Starikovskiy to do the same thing.
>
> The problem is one of logistics.
> As I've described before, the files with "R. Byron Moore" at the top are
> dual-licensed so Intel can distribute the core interpreter both as GPL
> to Linux and also to FreeBSD, HP-UX etc
Well, I can not speak for Adrian but if I were to submit a patch and state
that it is also dual licensed you should have no troubles applying it even
to the core files, right?
--
Dmitry
next prev parent reply other threads:[~2005-01-27 23:30 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 [this message]
2005-01-30 17:32 ` [2.6 patch] drivers/acpi/: make some code static Adrian Bunk
2005-01-30 17:39 ` [RFC: 2.6 patch] drivers/acpi/: possible cleanups Christoph Hellwig
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=200501271830.36444.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--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.