[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101104090050.GF5210@cr0.nay.redhat.com>
Date: Thu, 4 Nov 2010 17:00:50 +0800
From: Américo Wang <xiyou.wangcong@...il.com>
To: trapDoor <trapdoor6@...il.com>
Cc: Américo Wang <xiyou.wangcong@...il.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: Pure kernel '2.6.37-rc1-00001-ge99d11d' shown as ~-dirty after
compilation
On Wed, Nov 03, 2010 at 05:07:00PM +0000, trapDoor wrote:
>>>
>>>So, what's this '-dirty' about?
>>>
>>
>> That means your git tree is not clean, since you placed new firmwares
>> into the source tree.
>>
>
>OK, but then 'make kernelrelease' should produce the same '..-dirty'
>version, not just '2.6.37-rc1-00001-ge99d11d', shouldn't it?
>
Yes, it should.
>I always do the following steps in the same order:
>1) first I place the firmware files in <kernel-src>/firmware/radeon
>2) then I choose appropriate config file and copy it into kernel
>source directory
>3) then I run 'make oldconfig' and at the end - just before compiling
>and installing - 'make kernelrelease'
>
>As I mentioned, for none of the kernels I compiled prior to this
>version (either from git or from tarball) 'make kernelrelease'
>produced different version name than it came up after compilation.
>
Note, there are few generated files not listed in gitignore, thus
could cause your tree not to clean. For those files, we should
add them into .gitignore.
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists