From: Paul Mundt <lethal@linux-sh.org>
To: Tim Abbott <tabbott@ksplice.com>,
linux-kernel@vger.kernel.org, David Howells <dhowells@redhat.com>,
Anders Kaseorg <andersk@ksplice.com>
Subject: Re: [PATCH] Restructure BSS linker script macros.
Date: Mon, 20 Jul 2009 23:39:44 +0900 [thread overview]
Message-ID: <20090720143944.GA29422@linux-sh.org> (raw)
In-Reply-To: <20090717221336.GA7336@merkur.ravnborg.org>
On Sat, Jul 18, 2009 at 12:13:36AM +0200, Sam Ravnborg wrote:
> On Thu, Jul 16, 2009 at 06:58:50PM -0400, Tim Abbott wrote:
> > On Thu, 16 Jul 2009, Tim Abbott wrote:
> >
> > > On Thu, 16 Jul 2009, Sam Ravnborg wrote:
> > >
> > > > On Sun, Jul 12, 2009 at 06:23:33PM -0400, Tim Abbott wrote:
> > > > > I'd like acks from Sam and David on this one. Also CCing Paul, since
> > > > > he has a patch from me which will need to be updated to use
> > > > > BSS_SECTION(0, PAGE_SIZE, 4) once this gets merged.
> > [...]
> > > > Could you please resend including the necessary fix for mn10300 so we do not
> > > > break bisecting.
> > >
> > > I don't understand what you're asking here. The original patch I sent
> > > does include the necessary fix for mn10300 in the first hunk (reproduced
> > > below). I intentionally changed the mn10300 use at the same time as
> > > changing the macros in order to avoid breaking bisecting.
> >
> > I realized that you probably meant that I should resend the sh patch that
> > I have currently in linux-next via Paul's tree that is broken by this
> > change.
> >
> > Paul -- the patch below differs from the version have in two ways:
> > (1) I updated it to use the fixed BSS linker script macros from this
> > thread.
> > (2) I dropped the hunk that conflicted with a similar change in the percpu
> > tree[2], as the version of that change in the percpu tree is better.
>
> I do not expect Tejun's work to be included until next merge window.
> It would be nice if we could queue up a lot of vmlinux.lds
> cleanup patches so they are ready for next merge window.
> But we should rely on the arch maintainers mostly - as you nicely
> have done for sh here.
>
I've pulled your kbuild-fixes.git in to a topic branch with Tim's
BSS_SECTION fix applied over top of it, this seemed like the easiest way
to keep my tree building both in and out of -next. Once kbuild-fixes hits
Linus's tree it should all sort itself out anyways.
next prev parent reply other threads:[~2009-07-20 14:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-12 22:23 [PATCH] Restructure BSS linker script macros Tim Abbott
2009-07-16 18:20 ` Tim Abbott
2009-07-16 20:34 ` Sam Ravnborg
2009-07-16 20:46 ` Tim Abbott
2009-07-16 22:58 ` Tim Abbott
2009-07-17 22:06 ` Sam Ravnborg
2009-07-17 22:13 ` Sam Ravnborg
2009-07-20 14:39 ` Paul Mundt [this message]
2009-07-20 16:33 ` Tim Abbott
2009-07-20 16:36 ` Paul Mundt
2009-07-20 17:07 ` 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=20090720143944.GA29422@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=andersk@ksplice.com \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tabbott@ksplice.com \
/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.