From: Andrew Morton <akpm@linux-foundation.org>
To: Greg KH <gregkh@suse.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Dmitry Torokhov <dtor@insightbb.com>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] Input patches for 2.6.20
Date: Sat, 5 May 2007 00:08:32 -0700 [thread overview]
Message-ID: <20070505000832.66b8cf9e.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070505060338.GA27713@suse.de>
On Fri, 4 May 2007 23:03:38 -0700 Greg KH <gregkh@suse.de> wrote:
> Sorry about that, sometimes core changes like this take a bit of
> coordination across subsystems.
tell me about it.
I often end up maintaining patches which fix susbsystem A for subsystem B.
And patches which fix patch A for patch B:
box:/usr/src/25> grep '[-]vs-' series
fix-refrigerator-vs-thaw_process-race.patch
pata_acpi-restore-driver-vs-libata-clean-up-sff-init-mess-fix.patch
git-ioat-vs-git-md-accel.patch
#git-wireless-vs-git-net.patch
#git-wireless-vs-git-net-2.patch
#git-wireless-vs-git-net-3.patch
#mm-fix-fault-vs-invalidate-race-for-linear-mappings.patch: Hugh issues
mm-fix-fault-vs-invalidate-race-for-linear-mappings.patch
mm-debug-check-for-the-fault-vs-invalidate-race.patch
mm-fix-clear_page_dirty_for_io-vs-fault-race.patch
#git-block-vs-ext4-ext4-delayed-allocation.patch
call-cpu_chain-with-cpu_down_failed-if-cpu_down_prepare-failed-vs-reduce-size-of-task_struct-on-64-bit-machines.patch
workqueue-fix-flush_workqueue-vs-cpu_dead-race.patch
fix-kthread_create-vs-freezer-theoretical-race.patch
revoke-special-mmap-handling-vs-fault-vs-invalidate.patch
lguest-vs-x86_64-mm-use-per-cpu-variables-for-gdt-pda.patch
lguest-the-host-code-vs-x86_64-mm-i386-separate-hardware-defined-tss-from-linux-additions.patch
#lguest-the-host-code-vs-sys_futex64-allows-64bit-futexes-get_futex_key-must-check-proper-alignement-for-64bit-futexes.patch
lguest-the-host-code-vs-futex-new-private-futexes.patch
acpi-keep-tsc-stable-when-lapic_timer_c2_ok-is-set-vs-x86_64-mm-log-reason-why-tsc-was-marked-unstable.patch
#proc-maps-protection-vs-utrace.patch
#utrace-vs-reduce-size-of-task_struct-on-64-bit-machines.patch
make-copy_from_user_inatomic-not-zero-the-tail-on-i386-vs-reiser4.patch
#git-block reiser4-vs-git-block.patch
#git-block reiser4-vs-git-block-2.patch
#git-block reiser4-vs-git-block3.patch
#git-kgdb-vs-define-struct-pspace.patch
but it takes a little time to get these propagated into the right place..
next prev parent reply other threads:[~2007-05-05 7:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-18 7:04 [git pull] Input patches for 2.6.20 Dmitry Torokhov
2007-05-03 5:07 ` Dmitry Torokhov
2007-05-05 1:19 ` Linus Torvalds
2007-05-05 6:03 ` Greg KH
2007-05-05 7:08 ` Andrew Morton [this message]
2007-05-05 8:51 ` Martin Schwidefsky
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=20070505000832.66b8cf9e.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=cornelia.huck@de.ibm.com \
--cc=dtor@insightbb.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=torvalds@linux-foundation.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