mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Adrian Bunk <bunk@kernel.org>
Cc: Oliver Neukum <oliver@neukum.org>, linux-kernel@vger.kernel.org
Subject: Re: possible build system oddity
Date: Fri, 31 Aug 2007 11:00:27 -0400	[thread overview]
Message-ID: <26547.1188572427@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 31 Aug 2007 10:42:29 +0200." <20070831084229.GE9260@stusta.de>

[-- Attachment #1: Type: text/plain, Size: 756 bytes --]

On Fri, 31 Aug 2007 10:42:29 +0200, Adrian Bunk said:
> On Fri, Aug 31, 2007 at 10:37:28AM +0200, Oliver Neukum wrote:
> > Hi,
> > 
> > I only touched sound/usb/usbaudio.c
> > Nevertheless the whole subtree und sound/ is recompiling. What's
> > happening?
> 
> The only file that gets compiled (CC) should be sound/usb/usbaudio.c
> 
> It seems you are confused by the fact that this recompilation results in 
> several relinks (LD)?

Or something else changed that he didn't realize.  Just the other day, I
applied a one-line patch that hit one .c file, and *the entire kernel*
started rebuilding.

Took me a while to figure out that I'd been looking for something else, and
done a 'vi Makefile' in the top level, and exited with 'ZZ' rather than ':q' ;)


[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

  parent reply	other threads:[~2007-08-31 15:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-31  8:37 Oliver Neukum
2007-08-31  8:42 ` Adrian Bunk
2007-08-31 11:32   ` Oliver Neukum
2007-08-31 15:00   ` Valdis.Kletnieks [this message]
2007-08-31 16:30     ` Sam Ravnborg
2007-08-31 20:50     ` Jan Engelhardt
2007-08-31  9:14 ` Alexey Dobriyan
2007-08-31  9:47   ` Sam Ravnborg
2007-08-31  9:51     ` Oliver Neukum
2007-08-31 10:38       ` Jan Engelhardt
2007-08-31 10:46         ` Oliver Neukum

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=26547.1188572427@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=bunk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oliver@neukum.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

all inboxes | Powered by JetHome®