From: Sam Ravnborg <sam@ravnborg.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com, hpa@zytor.com,
hpa@c2micro.com, tglx@linutronix.de, hpa@linux.intel.com,
jeremy.fitzhardinge@citrix.com,
linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/urgent] x86: linker script: avoid ALIGN statements inside output sections
Date: Tue, 28 Apr 2009 12:00:23 +0200 [thread overview]
Message-ID: <20090428100023.GA18148@uranus.ravnborg.org> (raw)
In-Reply-To: <20090428090211.GD26487@elte.hu>
>
> Below is hpa's fix merged up by me on top of your cleanups. That
> merge-up is incomplete as we lose these fixlets.
>
> And in this form it's visible how we lose those cleanups you did -
> which werent really cleanups ... Please keep such side-effects apart
> from truly mechanic cleanups, whenever possible - it makes life
> really simpler.
The cleanup that you applied did NOT move any ALIGN() - or
at least not on purpose.
It was supposed to be a noop from a functionality point of view.
I have started to unify the the two vmlinux.lds files for
32 and 64 bit - and as part of that serie (yet to be published) you will
see individual commits where ALING() is moved and secitons
are reordered etc.
I do this in baby steps so we can track regressions using bisect.
The work is done on top of x86/kbuild and I will rebase as needed when
I have it ready.
Sam
next prev parent reply other threads:[~2009-04-28 9:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tip-c707f31e2e6af2d37bc742c31be0c7e96946c71f@git.kernel.org>
2009-04-28 8:14 ` [tip:x86/urgent] x86: linker script: avoid ALIGN statements inside output sections Ingo Molnar
2009-04-28 8:38 ` Sam Ravnborg
2009-04-28 9:02 ` Ingo Molnar
2009-04-28 10:00 ` Sam Ravnborg [this message]
2009-04-28 10:48 ` Ingo Molnar
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=20090428100023.GA18148@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=hpa@c2micro.com \
--cc=hpa@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jeremy.fitzhardinge@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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