From: Andrew Morton <akpm@linux-foundation.org>
To: Len Brown <lenb@kernel.org>
Cc: "Moore, Robert" <robert.moore@intel.com>,
trenn@suse.de, linux-acpi@vger.kernel.org, jbeulich@novell.com
Subject: Re: [patch 04/10] acpi: adjust _acpi_{module,function}_namedefinitions
Date: Thu, 26 Jun 2008 22:00:53 -0700 [thread overview]
Message-ID: <20080626220053.0a00a3c3.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.LFD.1.10.0806262210520.2988@localhost.localdomain>
On Thu, 26 Jun 2008 22:20:26 -0400 (EDT) Len Brown <lenb@kernel.org> wrote:
> In the future, please simply do not accept
> patches to drivers/acpi/*/* (the ACPICA files) into -mm.
Nope.
> Instead, bounce them to the Linux/ACPI maintainer,
> who will bounce them to the ACPICA maintainer --
> which is the head of the stream for these sub-directories.
One of the things I do is to act as backup for leaky maintainers. Many
years experience with hundreds of maintainers teaches me that they all
leak like sieves. Stuff which we *want* in the kernel would just get
lost if we relied upon maintainers to be 100% lossless.
Now, if both the Linux/ACPI maintainer and the ACPICA maintainer were
lossless then OK, but that would be unprecedented in my experience.
Even the best of the best (Mauro Chehab) loses stuff occasionally.
prev parent reply other threads:[~2008-06-27 5:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-01 9:52 [patch 04/10] acpi: adjust _acpi_{module,function}_name definitions akpm
2008-05-02 10:06 ` Thomas Renninger
2008-05-02 12:41 ` Andrew Morton
2008-05-02 14:04 ` Thomas Renninger
2008-05-04 19:14 ` [patch 04/10] acpi: adjust _acpi_{module,function}_namedefinitions Moore, Robert
2008-05-06 12:51 ` Thomas Renninger
2008-05-06 17:36 ` [patch 04/10] acpi: adjust_acpi_{module,function}_namedefinitions Moore, Robert
2008-06-23 19:45 ` [patch 04/10] acpi: adjust _acpi_{module,function}_namedefinitions Andrew Morton
2008-06-27 2:20 ` Len Brown
2008-06-27 5:00 ` Andrew Morton [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=20080626220053.0a00a3c3.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jbeulich@novell.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=robert.moore@intel.com \
--cc=trenn@suse.de \
/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.