From: Sam Ravnborg <sam@ravnborg.org>
To: "Yang, Fei" <fei.yang@intel.com>
Cc: "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: Mon, 26 Aug 2013 22:10:35 +0200 [thread overview]
Message-ID: <20130826201035.GA21141@merkur.ravnborg.org> (raw)
In-Reply-To: <02E7334B1630744CBDC55DA85862258348E431C1@ORSMSX102.amr.corp.intel.com>
On Mon, Aug 26, 2013 at 07:22:46PM +0000, Yang, Fei wrote:
> >From 5e6501efa26bc19dad0b43e3a2b0daa81408a8ae Mon Sep 17 00:00:00 2001
> From: Fei Yang <fei.yang@intel.com>
> Date: Mon, 26 Aug 2013 11:21:48 -0700
> Subject: [PATCH] FIXDEP: error opening depfile
>
> Met a kernel build issue where fixdep fails to open a depfile,
> fixdep: error opening depfile: drivers/driver-name/.driver-code.o.d: No such file or directory
> make[4]: *** [drivers/driver-name/driver-code.o] Error 2
> make[3]: *** [drivers/driver-name] Error 2
> Don't know why the expected file was not created, but the assumption that
> the file had been created might not be true, so simply return for such failure.
I tried to grep:
git grep "driver-name"
No hits.
Are you trying to fix a build issue with something out-of-tree - or is this only in linux-next?
Sam
next prev parent reply other threads:[~2013-08-26 20:10 UTC|newest]
Thread overview: 11+ 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 20:10 ` Sam Ravnborg [this message]
2013-08-27 19:05 ` Yang, Fei
2013-08-28 15:07 ` Michal Marek
2013-08-28 15:08 ` Michal Marek
2013-08-28 16:27 ` Yang, Fei
2013-08-28 16:31 ` Michal Marek
2013-08-28 16:47 ` Yang, Fei
2013-08-29 17:55 ` Sam Ravnborg
2013-08-30 15:10 ` Michal Marek
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=20130826201035.GA21141@merkur.ravnborg.org \
--to=sam@ravnborg.org \
--cc=fei.yang@intel.com \
--cc=linux-kbuild@vger.kernel.org \
--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