From: Andrew Morton <akpm@linux-foundation.org>
To: Pavel Machek <pavel@suse.cz>
Cc: linux-kernel@vger.kernel.org, eric.piel@tremplin-utc.net,
mm-commits@vger.kernel.org
Subject: Re: - lis3lv02d-separate-the-core-from-hp-acpi-api.patch removed from -mm tree
Date: Fri, 9 Jan 2009 15:23:17 -0800 [thread overview]
Message-ID: <20090109152317.ca2a2da8.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090109230003.GB2223@elf.ucw.cz>
On Sat, 10 Jan 2009 00:00:03 +0100
Pavel Machek <pavel@suse.cz> wrote:
> > The patch titled
> > LIS3LV02D: separate the core from HP ACPI API
> > has been removed from the -mm tree. Its filename was
> > lis3lv02d-separate-the-core-from-hp-acpi-api.patch
> >
> > This patch was dropped because other changes were merged, which wrecked this patch
>
> I'm confused. The other patch collided with leds/Makefile changes, but
> this one applies cleanly over Linus' git (updated today)... or am I
> doing something wrong? Could it still be pushed to Linus?
umm, sure, we can try that.
Please don't use vague terms like "the other patch". I assume you're
referring to lis3lv02d-merge-with-leds-hp-disk.patch?
It has more problems than a simple makefile conflict. People keep on
changing stuff in linux-next.
next prev parent reply other threads:[~2009-01-09 23:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 19:58 - lis3lv02d-separate-the-core-from-hp-acpi-api.patch removed from -mm tree akpm
2009-01-09 23:00 ` Pavel Machek
2009-01-09 23:23 ` Andrew Morton [this message]
2009-01-09 23:37 ` Éric Piel
2009-01-09 23:55 ` Andrew Morton
2009-01-10 23:31 ` [rediffed] lis3lv02d merge with leds hp disk Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2009-01-12 19:58 - lis3lv02d-separate-the-core-from-hp-acpi-api.patch removed from -mm tree akpm
2009-01-12 20:30 ` Pavel Machek
2009-01-12 20:49 ` Andrew Morton
2009-01-12 21:09 ` Harvey Harrison
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=20090109152317.ca2a2da8.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=eric.piel@tremplin-utc.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=pavel@suse.cz \
/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.