From: Tim Abbott <tabbott@ksplice.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/4] kbuild: Don't define ALIGN and ENTRY when preprocessing linker scripts.
Date: Sun, 20 Sep 2009 17:24:50 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.1.10.0909201718490.3101@dr-wily.mit.edu> (raw)
In-Reply-To: <20090920211627.GB27042@merkur.ravnborg.org>
On Sun, 20 Sep 2009, Sam Ravnborg wrote:
> The reason for __XXX___ for ASSEMBLY and KERNEL is the fact
> that these are used in user space headers.
>
> I would suggest to use: LINKER_SCRIPT
OK. I'm happy with calling it LINKER_SCRIPT.
> This will conflict (in a trivial way) with stuff I have
> pending for this merge window.
Is that pending stuff available in a public git repository somewhere? If
so, I could send you a version on top of those pending changes.
(Alternatively, if you're planning to take this patch, I'd be fine with
your resolving the merge conflict, updating the name, and putting it in
with your stuff. Whatever's easier for you).
-Tim Abbott
next prev parent reply other threads:[~2009-09-20 21:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-20 18:43 [PATCH v3 0/4] Use macros rather than hardcoding section names Tim Abbott
2009-09-20 18:43 ` [PATCH v3 1/4] kbuild: Don't define ALIGN and ENTRY when preprocessing linker scripts Tim Abbott
2009-09-20 21:16 ` Sam Ravnborg
2009-09-20 21:24 ` Tim Abbott [this message]
2009-09-20 21:43 ` Sam Ravnborg
2009-09-20 18:43 ` [PATCH v3 2/4] Use new __init_task_data macro in arch init_task.c files Tim Abbott
2009-09-20 18:43 ` [PATCH v3 3/4] Use macros for .bss.page_aligned section Tim Abbott
2009-09-20 18:43 ` [PATCH v3 4/4] Use macros for .data.page_aligned section Tim Abbott
2009-09-21 7:57 ` Martin Schwidefsky
2009-09-21 8:05 ` 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=alpine.DEB.1.10.0909201718490.3101@dr-wily.mit.edu \
--to=tabbott@ksplice.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®