From: Kyle McMartin <kyle@mcmartin.ca>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Kyle McMartin <kyle@mcmartin.ca>,
Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: [PATCH] fix compile failure with non-modular builds
Date: Thu, 11 Sep 2008 12:06:31 -0400 [thread overview]
Message-ID: <20080911160631.GB31713@phobos.i.cabal.ca> (raw)
In-Reply-To: <1221148954.3330.6.camel@localhost.localdomain>
On Thu, Sep 11, 2008 at 11:02:34AM -0500, James Bottomley wrote:
> On Thu, 2008-09-11 at 12:01 -0400, Kyle McMartin wrote:
> > On Thu, Sep 11, 2008 at 10:56:15AM -0500, James Bottomley wrote:
> > > commit deac93df26b20cf8438339b5935b5f5643bc30c9
> > > Author: James Bottomley <James.Bottomley@HansenPartnership.com>
> > > Date: Wed Sep 3 20:43:36 2008 -0500
> > >
> > > lib: Correct printk %pF to work on all architectures
> > >
> > > Broke the non modular builds by moving an essential function into
> > > modules.c. Fix this by moving it out again and into asm/sections.h as
> > > an inline.
> > >
> > > Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>
> >
> > Ack. Want to just fire it off to the big penguin, or should I submit it
> > with the unwind fix in the meantime?
>
> We have this, that and the RTC fix ... I'd say that's enough to maintain
> a tree.
>
Yeah, I cherrypicked from the parisc-2.6 branch for 2.6.27 (crap,
haven't pushed the tree out, my bad.) I didn't want to 'rename' the tree
since sfr is using "parisc-2.6" to mean "parisc-next-2.6" right now.
I'll push out a parisc-2.6.27.git tree later today.
r, Kyle
prev parent reply other threads:[~2008-09-11 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 15:56 [PATCH] fix compile failure with non-modular builds James Bottomley
2008-09-11 16:01 ` Kyle McMartin
2008-09-11 16:02 ` James Bottomley
2008-09-11 16:06 ` Kyle McMartin [this message]
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=20080911160631.GB31713@phobos.i.cabal.ca \
--to=kyle@mcmartin.ca \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-parisc@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 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.