DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        b=QO75q1tfAfQpENRSJjPVcyW1lUlllUwVkUuKk6q/QMMEbwVClIg8SBOURBgH14rFfk
         lx6kQ1JM/Ya2Z5IG1ZBaDSYCN+LBqbEpAlShi0bXp4nuiPPjPiRwWg4xMOnO5CbW6uQe
         q/z1W+01/2WKIRBx3/+OsGx86gQTASreh0O6c=
MIME-Version: 1.0
Date: Sun, 22 Mar 2009 11:43:28 +0100
Message-ID: <2d05c4580903220343l4b1359fx79f18b56203bd463@mail.gmail.com>
Subject: Test some kernel feature without recompile
From: Dragoslav Zaric <dragoslav.zaric.kd@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 780
Lines: 22

Hi,

I know when you work on some kernel module, you can change code and load
module again and test it, but what if you change some built in kernel
.c file, why
would I need to recompile whole kernel just to see what happens if I change one
.c file ??

Why can I just compile one changed .c file and copy it where compiled version of
that file reside inside kernel tree? Or maybe there is some image info embedded
inside compiled files, so that file must belong to specific image from
which it is
installed ?

Thanks,

Dragoslav Zaric
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/