public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Eric Miao <eric.y.miao@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kbuild: include only necessary in scripts/Makefile.modbuiltin
Date: Wed, 06 Jan 2010 11:39:07 +0100	[thread overview]
Message-ID: <4B44684B.1060401@suse.cz> (raw)
In-Reply-To: <f17812d71001060231l5c0ca1bha50e395790d0fc0b@mail.gmail.com>

On 6.1.2010 11:31, Eric Miao wrote:
> On Wed, Jan 6, 2010 at 5:51 PM, Michal Marek <mmarek@suse.cz> wrote:
>> On 6.1.2010 07:26, Eric Miao wrote:
>>> scripts/Makefile.modbuiltin assumes either Kbuild or Makefile exists in
>>> every sub-directory, which is not true.
>>
>> It assumes what there is a kbuild file in each directory listed in
>> subdir-[ym] or obj-[ym]. For which directory is this not true? Did you
>> see an actual build failure? The same include is used in
>> scripts/Makefile.build, where it has been working fine for ages...
>>
> 
> Well, it's in my tree outside mainline, I have to make this change
> to get it build. And'm wondering if that's a correct assumption.

And scripts/Makefile.build does not fail? Strange. Can you point me at
the tree so that I can have a look? I assume it's some branch of
git://git.kernel.org/pub/scm/linux/kernel/git/ycmiao/pxa-linux-2.6.git.

Thanks,
Michal

  reply	other threads:[~2010-01-06 10:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-06  6:26 [PATCH] kbuild: include only necessary in scripts/Makefile.modbuiltin Eric Miao
2010-01-06  9:51 ` Michal Marek
2010-01-06 10:31   ` Eric Miao
2010-01-06 10:39     ` Michal Marek [this message]
2010-01-06 11:22       ` Eric Miao
2010-01-06 11:47         ` Michal Marek
2010-01-06 11:59           ` Eric Miao

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=4B44684B.1060401@suse.cz \
    --to=mmarek@suse.cz \
    --cc=eric.y.miao@gmail.com \
    --cc=linux-kernel@vger.kernel.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