All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: "Yang, Fei" <fei.yang@intel.com>
Cc: Sam Ravnborg <sam@ravnborg.org>,
	"linux-kbuild@vger.kernel.org" <linux-kbuild@vger.kernel.org>,
	"'linux-kernel@vger.kernel.org' (linux-kernel@vger.kernel.org)" 
	<linux-kernel@vger.kernel.org>
Subject: Re: Can anyone suggest a better fix? Not sure if I understand the problem, but the patch fixed it
Date: Wed, 28 Aug 2013 18:31:01 +0200	[thread overview]
Message-ID: <521E25C5.2020908@suse.cz> (raw)
In-Reply-To: <02E7334B1630744CBDC55DA85862258348E4792D@ORSMSX102.amr.corp.intel.com>

Dne 28.8.2013 18:27, Yang, Fei napsal(a):
> I thought fixdep is about finding module dependency, and it isn't
> needed for built-in drivers. Please correct me if I'm wrong.

fixdep filters the *.d files generated by gcc. These files record source
-> object file dependencies, to not miss rebuilds.

Michal

  reply	other threads:[~2013-08-28 16:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-26 19:22 Can anyone suggest a better fix? Not sure if I understand the problem, but the patch fixed it Yang, Fei
2013-08-26 19:22 ` Yang, Fei
2013-08-26 20:10 ` Sam Ravnborg
2013-08-26 20:10   ` Sam Ravnborg
2013-08-27 19:05   ` Yang, Fei
2013-08-27 19:05     ` Yang, Fei
2013-08-28 15:07     ` Michal Marek
2013-08-28 15:07       ` Michal Marek
2013-08-28 15:08       ` Michal Marek
2013-08-28 15:08         ` Michal Marek
2013-08-28 16:27       ` Yang, Fei
2013-08-28 16:27         ` Yang, Fei
2013-08-28 16:31         ` Michal Marek [this message]
2013-08-28 16:31           ` Michal Marek
2013-08-28 16:47           ` Yang, Fei
2013-08-28 16:47             ` Yang, Fei
2013-08-29 17:55         ` Sam Ravnborg
2013-08-29 17:55           ` Sam Ravnborg
2013-08-30 15:10           ` Michal Marek
2013-08-30 15:10             ` Michal Marek
2013-08-29 17:55         ` Sam Ravnborg
2013-08-29 17:55           ` Sam Ravnborg

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=521E25C5.2020908@suse.cz \
    --to=mmarek@suse.cz \
    --cc=fei.yang@intel.com \
    --cc=linux-kbuild@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.