From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Kujau Subject: Re: [Alsa-devel] Oops in 2.6.10-rc1 Date: Thu, 04 Nov 2004 16:16:11 +0100 Message-ID: <418A47BB.5010305@g-house.de> References: <4180F026.9090302@g-house.de> <4180FDB3.8080305@g-house.de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4180FDB3.8080305@g-house.de> Sender: linux-kernel-owner@vger.kernel.org To: LKML Cc: alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hm, still no sound with snd_ens1371 but now i spend some time to find out how to revert a patch with bk. while compiling is still ongoing, let me tell you how i tried to revert the patch with bk, because i am not entirely sure if i do the right thing here: bk changes > ../changes-04-11-2004.txt as written before, i suspect (!) two changes here: > [...] > > [PATCH] i386/io_apic init section fixups > > > [PATCH] vm: convert users of remap_page_range() under sound/ to > use remap_pfn_range() > [...] > > so i'll revert the patches and see what it gives. in ../changes-04-11-2004.txt i found out the ChnageSet numbers: 1.1988.72.76 + 1.2000.5.77. then i did bk undo -a1.1988.72.76 only to find out that i misread the manual and 1.1988.72.76 is still in place. i did bk changes > ../changes-1.1988.72.76.txt and the very patch has a different ChangeSet now: 1.2202. so i did bk undo -a1.2201 is this the right way to revert patches when subsequent patches might not allow to simply "bk undo -r" (because subsequent patches rely on this single ChangeSet). thank you for your assistance, Christian - -- BOFH excuse #182: endothermal recalibration -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBike6+A7rjkF8z0wRAl/DAKDAMP31cXrzjBnnl+713F1zJ5ShQQCdFYRr TpRkMTwdhZq9SvoZEPR2Plw= =sm2q -----END PGP SIGNATURE-----