From: Paul Jackson <pj@sgi.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, Simon.Derr@bull.net
Subject: How do I remove a patch buried in your *-mm series?
Date: Sat, 3 Dec 2005 23:49:00 -0800 [thread overview]
Message-ID: <20051203234900.fcaa6caf.pj@sgi.com> (raw)
I want to remove the patch in *-mm:
1) cpuset-change-marker-for-relative-numbering.patch
Unfortunately, it collides with another couple cpuset patches later in
your stack:
2) cpuset-memory-pressure-meter.patch, cpuset-memory-pressure-meter-gcc-295-fix.patch
How should I do this so I minimize the amount of cussing you do in my
general direction:
A. Just ask you to nuke patch (1) above; let you edit the mess.
B. Ask you to nuke both (1) and (2); leave me to resend a (2) that applies.
C. Send a reversing patch that applies on top of your current *-mm stack.
D. Some other plan you would prefer.
I have verified that removing all the patches above applies cleanly and
builds, with just a harmless -74 lines offset on one of the remaining
cpuset patches.
So I recommend B.
Separately I will send a patch to remove the bit of Documentation/cpusets.txt
that described this feature.
Details for the historical record:
I either need to go one step forward with it (fix a bug so that
it zeros the marker_pid of the left behind cpuset when attach_task
moves a task), or I need to go five steps backward, with a different
approach. But I have other stuff to do first, so should avoid
digging this "change-marker-for-relative-numbering" any deeper
than it is for now.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
next reply other threads:[~2005-12-04 7:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-04 7:49 Paul Jackson [this message]
2005-12-04 8:15 ` How do I remove a patch buried in your *-mm series? Andrew Morton
2005-12-04 8:31 ` Paul Jackson
2005-12-04 8:44 ` Andrew Morton
2005-12-04 9:08 ` Paul Jackson
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=20051203234900.fcaa6caf.pj@sgi.com \
--to=pj@sgi.com \
--cc=Simon.Derr@bull.net \
--cc=akpm@osdl.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