From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: arch/arm64/efi-stub.o rebuilding every time?
Date: Fri, 4 Jul 2014 09:24:42 +0100 [thread overview]
Message-ID: <20140704082442.GE23379@arm.com> (raw)
In-Reply-To: <1404455777.3649.154.camel@mfleming-mobl1.ger.corp.intel.com>
On Fri, Jul 04, 2014 at 07:36:17AM +0100, Matt Fleming wrote:
> On Thu, 2014-07-03 at 16:16 +0200, Ard Biesheuvel wrote:
> > On 3 July 2014 16:13, Will Deacon <will.deacon@arm.com> wrote:
> > > Hi guys,
> > >
> > > If I build an arm64 kernel, then simply hit make again without changing
> > > anything, I find that efi-stub.o is rebuilt every time (with an annoying
> > > warning too, but I think you already know about that):
> > >
> >
> > Yep, I had noticed that as well. The reason is that it depends on
> > generated header files, which it shouldn't. There's already a patch
> > queued in Matt Fleming's tree for this:
> > https://git.kernel.org/cgit/linux/kernel/git/mfleming/efi.git/commit/?h=next&id=86b2eb8cdffda7eef07b1d6e5464491df1e86ee9
>
> It sounds like that commit should actually be put into my 'urgent'
> branch and sent to tip asap instead of being queued up for the next
> merge window.
>
> Objections?
Sounds good to me. You can also add my ack, if you like:
Acked-by: Will Deacon <will.deacon@arm.com>
Will
next prev parent reply other threads:[~2014-07-04 8:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 14:13 arch/arm64/efi-stub.o rebuilding every time? Will Deacon
2014-07-03 14:16 ` Ard Biesheuvel
2014-07-04 6:36 ` Matt Fleming
2014-07-04 8:24 ` Will Deacon [this message]
2014-07-04 8:53 ` Ard Biesheuvel
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=20140704082442.GE23379@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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.