public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Hounschell <markh@compro.net>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Alex Deucher <alexdeucher@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: kernel tree "diff -urN" anomaly?
Date: Fri, 03 Dec 2010 16:03:30 -0500	[thread overview]
Message-ID: <4CF95B22.3010206@compro.net> (raw)
In-Reply-To: <20101203204709.GA17591@merkur.ravnborg.org>

On 12/03/2010 03:47 PM, Sam Ravnborg wrote:
> On Fri, Dec 03, 2010 at 02:49:03PM -0500, Mark Hounschell wrote:
>> I start with two clean identical 2.6.36.1 kernel trees (different names
>> of coarse). I build one of them. I then do a "make clean mrproper" in
>> the tree I built. Why then does the diff command in the subject line
>> find the following files changed?
>>
>> drivers/gpu/drm/radeon/evergreen_reg_safe.h
>> drivers/gpu/drm/radeon/r100_reg_safe.h
>> drivers/gpu/drm/radeon/r200_reg_safe.h
>> drivers/gpu/drm/radeon/r300_reg_safe.h
>> divers/gpu/drm/radeon/r420_reg_safe.h
>> drivers/gpu/drm/radeon/r600_reg_safe.h
>> drivers/gpu/drm/radeon/rn50_reg_safe.h
>> drivers/gpu/drm/radeon/rs600_reg_safe.h
>> drivers/gpu/drm/radeon/rv515_reg_safe.h
> 
> Files are generated during the build.
> So after you have build your kernel the files are present.
> And the Makefile is missing logic to delete the files during "make clean".
> 

OK, broken Makefile then

Thanks
Mark

      reply	other threads:[~2010-12-03 21:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-03 19:49 kernel tree "diff -urN" anomaly? Mark Hounschell
2010-12-03 20:47 ` Sam Ravnborg
2010-12-03 21:03   ` Mark Hounschell [this message]

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=4CF95B22.3010206@compro.net \
    --to=markh@compro.net \
    --cc=alexdeucher@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    /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