From: Andrew Morton <akpm@osdl.org>
To: Len Brown <lenb@kernel.org>
Cc: Len Brown <len.brown@intel.com>,
Jan Engelhardt <jengelh@linux01.gwdg.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ACPI List <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH] Cast removal
Date: Wed, 4 Oct 2006 22:19:14 -0700 [thread overview]
Message-ID: <20061004221914.0811b28a.akpm@osdl.org> (raw)
In-Reply-To: <200610050043.41997.len.brown@intel.com>
On Thu, 5 Oct 2006 00:43:41 -0400
Len Brown <len.brown@intel.com> wrote:
> On Thursday 05 October 2006 00:12, Andrew Morton wrote:
> > On Wed, 4 Oct 2006 23:56:02 -0400
> > Len Brown <len.brown@intel.com> wrote:
> >
> > > I'm okay applying this patch it touches the linux-specific
> > > drivers/acpi/* files only, no ACPICA files.
> >
> > Why?
>
> Why am I okay with it?
No, I meant why not clean up ACPICA too?
> If maintaining individual ACPI-related patches in -mm is a burden,
> then refuse to.
Not an especial burden, but it would be nice to get more acks or nacks when
I send them over. scsi is a bit of a problem in this regard too.
next prev parent reply other threads:[~2006-10-05 5:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-30 22:28 [PATCH] Cast removal Jan Engelhardt
2006-10-05 3:56 ` Len Brown
2006-10-05 4:12 ` Andrew Morton
2006-10-05 4:43 ` Len Brown
2006-10-05 5:19 ` Andrew Morton [this message]
2006-10-05 8:00 ` Jan Engelhardt
-- strict thread matches above, loose matches on Subject: below --
2006-10-04 21:40 Moore, Robert
2006-10-05 0:28 ` Andrew Morton
2006-10-05 15:45 Moore, Robert
2006-10-05 22:14 Moore, Robert
2006-10-05 22:26 ` Andrew Morton
2006-10-06 5:34 ` Jan Engelhardt
2006-10-06 14:35 ` Muli Ben-Yehuda
2006-10-06 20:18 ` Jan Engelhardt
2006-10-06 20:30 ` Muli Ben-Yehuda
2006-10-06 20:39 ` Arjan van de Ven
2006-10-05 22:23 Brown, Len
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=20061004221914.0811b28a.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=jengelh@linux01.gwdg.de \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox