From: Sam Ravnborg <sam@ravnborg.org>
To: Adrian Bunk <bunk@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: [GIT PULL] kbuild fixes
Date: Sat, 26 Apr 2008 21:37:01 +0200 [thread overview]
Message-ID: <20080426193701.GA9131@uranus.ravnborg.org> (raw)
In-Reply-To: <20080426192037.GR2252@cs181133002.pp.htv.fi>
On Sat, Apr 26, 2008 at 10:20:37PM +0300, Adrian Bunk wrote:
> On Sat, Apr 26, 2008 at 09:12:56PM +0200, Sam Ravnborg wrote:
> > Hi Linus.
> >
> > Please apply the following two fixes by pulling from:
> >
> > master.kernel.org/pub/scm/linux/kernel/git/sam/kbuild.git
> >
> >
> > The MODULE_LICENSE fix is neded to get an allmodconfig
> > build fixed.
>
> Which one is this?
>
> http://lkml.org/lkml/2008/3/31/50 ?
> (my allmod build is not yet finished)
The changelog was actually bad for this one.
I saw two classes of problems:
1) I got report about broken builds - fbdev was the culprint.
2) a "make CONFIG_DEBUG_SECTION_MISMATCH=y" build broke
immediately.
I made it non-fatal because we had at least one module that
was not yet fixed.
Sam
next prev parent reply other threads:[~2008-04-26 19:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-26 19:12 Sam Ravnborg
2008-04-26 19:20 ` Adrian Bunk
2008-04-26 19:37 ` Sam Ravnborg [this message]
2008-04-26 19:49 ` Sam Ravnborg
2008-04-26 19:55 ` Adrian Bunk
2008-04-26 20:05 ` Adrian Bunk
2008-05-04 19:13 Sam Ravnborg
2008-05-25 7:12 Sam Ravnborg
2008-05-25 18:31 ` Sam Ravnborg
2008-05-25 21:10 ` Sam Ravnborg
2008-08-04 21:01 Sam Ravnborg
2008-08-06 20:27 Sam Ravnborg
2008-08-07 9:18 ` Russell King
2009-10-11 22:18 Sam Ravnborg
2009-10-12 8:41 ` Michael Tokarev
2009-10-13 15:10 ` Américo Wang
2009-10-13 18:58 ` Sam Ravnborg
2009-10-13 19:19 ` Michael Tokarev
2009-10-13 20:20 ` Sam Ravnborg
2009-10-14 6:43 ` Michael Tokarev
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=20080426193701.GA9131@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=bunk@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome