From: "Tony Luck" <tony.luck@intel.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [git pull] ia64 change (include/asm-ia64 -> arch/ia64/include/asm)
Date: Sat, 02 Aug 2008 18:09:54 +0000 [thread overview]
Message-ID: <12c511ca0808021109x78227335v4c39f1098a4bfeee@mail.gmail.com> (raw)
In-Reply-To: <57C9024A16AD2D4C97DC78E552063EA3082ABD3A@orsmsx505.amr.corp.intel.com>
On Sat, Aug 2, 2008 at 10:14 AM, Robin Holt <holt@sgi.com> wrote:
> Just a minor nit that I can't figure out. Following a build, a
> git-status shows untracked files of:
>
> # Untracked files:
> # (use "git add <file>..." to include in what will be committed)
> #
> # arch/ia64/kernel/vmlinux.lds
> # include/asm-ia64/
>
> I posted a change for the vmlinux.lds (or maybe it was just a question),
I think I remember that ... but I can't find it in the e-mail
archives. vmlinux.lds
needs to be added to .gitignore
> but I am not sure what to do with include/asm-ia64/. It contains two
> files that are generated:
> asm-offsets.h nr-irqs.h
>
> I get the feeling we should be generating those into
> arch/ia64/include/asm, but I am not certain.
Sam said in reply to a similar question:
asm-offsets.h is a generated file and I wanted to avoid adding
generated files to arch/$ARCH/include.
It was also a less intrusive patch to keep it at the old location.
But I recall that it troubles me a bit before I got it
correct but the kbuild changes all take care of this.
So this is currently correct ... but it sounds like it may change if
someone comes up with a better idea for where generated header
files should go.
-Tony
next prev parent reply other threads:[~2008-08-02 18:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-01 21:50 [git pull] ia64 change (include/asm-ia64 -> arch/ia64/include/asm) Luck, Tony
2008-08-02 17:14 ` [git pull] ia64 change (include/asm-ia64 -> Robin Holt
2008-08-02 18:09 ` Robin Holt
2008-08-02 18:09 ` Tony Luck [this message]
2008-08-02 21:56 ` [git pull] ia64 change (include/asm-ia64 -> arch/ia64/include/asm) 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=12c511ca0808021109x78227335v4c39f1098a4bfeee@mail.gmail.com \
--to=tony.luck@intel.com \
--cc=linux-ia64@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