mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Miles Lane <miles.lane@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	linux1394-devel@lists.sourceforge.net
Subject: Re: 2.6.18-rc5-mm1 + all hotfixes -- INFO: possible recursive locking detected
Date: Tue, 05 Sep 2006 22:19:51 +0200	[thread overview]
Message-ID: <44FDDBE7.1040906@s5r6.in-berlin.de> (raw)
In-Reply-To: <a44ae5cd0609051249y767eed58ja1fe1b27858f5cd@mail.gmail.com>

Miles Lane wrote:
> I am having trouble with backing out the git-ieee1394 patches. 

Take a look at
http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc5/2.6.18-rc5-mm1/broken-out/series

There are a number of 1394 subsystem patches; the last one is
ieee1394-sbp2-more-help-in-kconfig.patch. (That's supposed that no
further external patches touch ieee1394.) The order of patches in
patch-series is how they were applied.

Not all of these patches depend on each other, but some do. So the
safest way to unapply them is to follow the exact reverse order.

One tool to make this a little bit easier is quilt. This should be
available as a package for most distributions. I haven't tried it myself
yet, but akpm's "broken-out" patch distribution can be manipulated by
quilt. I guess it works like the following method --- which has the
drawback that you cannot use it with your existing linux-2.6.18-rc5-mm1
build. (Except with a trick, see below.)

Install linux-2.6.18-rc5.
Unpack
http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc5/2.6.18-rc5-mm1/2.6.18-rc5-mm1-broken-out.tar.bz2

Rename the broken-out directory to "linux-2.6.18-rc5/patches".
Copy your linux-2.6.18-rc5-mm1/.config to linux-2.6.18-rc5.

Apply all the patches, in the order given by patches/series:
$ cd linux-2.6.18-rc5
$ quilt push -a

Fetch all of
http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc5/2.6.18-rc5-mm1/hot-fixes/
and add it on top of all regular mm1 patches:
$ quilt import ~/hot-fixes/*.patch
$ quilt push -a

Now open patches/series in an editor. Find the ieee1394 patches. Move
all of them to the bottom of the series file. Save it. You can now
revert each 1394 patch by
$ quilt pop

Build the kernel as usual.

Now to the trick I mentioned before. To avoid starting from
linux-2.6.18-rc5 even though you already built and booted
2.6.18-rc5-mm1, perform the steps above on top of 2.6.18-rc5 until and
including the step where you imported and pushed the hot-fixes. After
that, just copy the patches/ and .pc/ directories over to your existing
2.6.18-rc5-mm1. Check the effect with
$ cd ../2.6.18-rc5-mm1
$ quilt top
This should give a message that the last hot fix is topmost. It should
now be possible to run "quilt pop" etc.

Anyway; manually removing the ieee1394 patches by looking at the order
in the series file may be faster than setting up quilt and the second
kernel source tree.
-- 
Stefan Richter
-=====-=-==- =--= --=-=
http://arcgraph.de/sr/

  reply	other threads:[~2006-09-05 20:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-05 17:37 Miles Lane
2006-09-05 18:13 ` Andrew Morton
2006-09-05 18:16   ` Miles Lane
2006-09-05 19:03     ` Stefan Richter
2006-09-05 19:19       ` Miles Lane
2006-09-05 19:51         ` Stefan Richter
2006-09-05 19:23   ` Stefan Richter
2006-09-05 21:07     ` Arjan van de Ven
2006-09-05 22:27       ` Stefan Richter
2006-09-06  0:10         ` Adrian Bunk
2006-09-06  7:13     ` Stefan Richter
2006-09-06 16:50       ` Stefan Richter
2006-09-06 17:04         ` [RFT PATCH 1/2] ieee1394: nodemgr: fix rwsem recursion Stefan Richter
2006-09-06 17:06           ` [RFT PATCH 2/2] ieee1394: nodemgr: grab class.subsys.rwsem in nodemgr_resume_ne Stefan Richter
2006-09-07 22:45         ` 2.6.18-rc5-mm1 + all hotfixes -- INFO: possible recursive locking detected Miles Lane
2006-09-07 23:23           ` Stefan Richter
2006-09-06 22:35       ` Greg KH
2006-09-05 19:49   ` Miles Lane
2006-09-05 20:19     ` Stefan Richter [this message]
2006-09-05 20:26       ` Stefan Richter
2006-09-05 20:33       ` Andrew Morton
2006-09-06  6:39 ` Arjan van de Ven

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=44FDDBE7.1040906@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=akpm@osdl.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=miles.lane@gmail.com \
    /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

Powered by JetHome