From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: trapDoor <trapdoor6@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Pure kernel '2.6.37-rc1-00001-ge99d11d' shown as ~-dirty after compilation
Date: Thu, 4 Nov 2010 00:48:40 +0800 [thread overview]
Message-ID: <20101103164840.GC4683@hack> (raw)
In-Reply-To: <AANLkTik=04z2thHBS3Z9n68QnTs=i8g8qTFtNT3jb8cg@mail.gmail.com>
On Tue, Nov 02, 2010 at 08:26:59AM +0000, trapDoor wrote:
>,Hello,
>When I run 'make kernelrelease' on freshly cloned Linus' git tree it
>shows kernel version as: '2.6.37-rc1-00001-ge99d11d' - and that's
>correct.
>But after compilation it turned up '2.6.37-rc1-00001-ge99d11d-dirty'.
>
>I didn't apply any custom patches to my local tree between 'make
>kernelrelease' and compilation. What I only added - and before running
>'make kernelrelease' - were the following Radeon firmware blobs for my
>graphic card, which I placed in <kernel-source>/firmware/radeon/, in
>order to compile them in:
>REDWOOD_me.bin
>REDWOOD_pfp.bin
>REDWOOD_rlc.bin
>
>That's how I always did and none of the git-kernels I compiled before
>was referred to as '-dirty' due to the firmware blobs added manually.
>Also, the kernel version shown by 'make kernelrelease' never differed
>from the final kernel version after compilation. Of course assuming
>that no patches were applied in the meantime and no extra string was
>appended manually to the kernel version.
>
>So, what's this '-dirty' about?
>
That means your git tree is not clean, since you placed new firmwares
into the source tree.
--
Live like a child, think like the god.
next prev parent reply other threads:[~2010-11-03 16:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 8:26 trapDoor
2010-11-03 16:48 ` Américo Wang [this message]
2010-11-03 17:07 ` trapDoor
2010-11-03 18:35 ` trapDoor
2010-11-04 9:07 ` Américo Wang
2010-11-04 9:00 ` Américo Wang
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=20101103164840.GC4683@hack \
--to=xiyou.wangcong@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trapdoor6@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
all inboxes | Powered by JetHome®