Return-path: Received: from mail-gx0-f174.google.com ([209.85.161.174]:33308 "EHLO mail-gx0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756292Ab0KNQS6 (ORCPT ); Sun, 14 Nov 2010 11:18:58 -0500 Received: by gxk23 with SMTP id 23so2593244gxk.19 for ; Sun, 14 Nov 2010 08:18:57 -0800 (PST) Message-ID: <4CE00BEE.8060100@lwfinger.net> Date: Sun, 14 Nov 2010 10:18:54 -0600 From: Larry Finger MIME-Version: 1.0 To: James Womack CC: linux-wireless@vger.kernel.org Subject: Re: r8187se panic References: <4CDC9FA5.10002@lwfinger.net> <4CDD3BC4.7070102@lwfinger.net> <4CDD66C4.10603@lwfinger.net> <4CDD7945.70005@lwfinger.net> <4CDEDC74.3040902@lwfinger.net> <4CDEEEE4.80801@lwfinger.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: On 11/14/2010 06:22 AM, James Womack wrote: > Okay, I've downloaded the necessary tools and extracted the kernel > source. I have a tutorial on how to patch and build the kernel. Where > should I apply your patches? Change directory to the main directory of the kernel source - the one with subdirectories like arch, block, crypto, drivers, etc. Apply patches with a command of the form patch -p1 --dry-run < If that works without any error, then leave out the "--dry-run" to apply the patch. If/when it is necessary to remove the patch, adding a "-R" option will do that. When you build the kernel, you should do that as a normal user, not root. If the source files are not owned by that user, you should do a chown on that tree before starting. Larry