From: Ben Dooks <ben-linux@fluff.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Michael Buesch <mb@bu3sch.de>,
Gordon Farquharson <gordonfarquharson@gmail.com>,
Russell King <rmk+lkml@arm.linux.org.uk>,
linux-kernel@vger.kernel.org, linville@tuxdriver.com,
stefano.brivio@polimi.it, Linus Torvalds <torvalds@osdl.org>,
Andrew Morton <akpm@osdl.org>,
viro@ftp.linux.org.uk
Subject: Re: [RFC] [PATCH] Fix b43 driver build for arm
Date: Tue, 26 Feb 2008 14:37:45 +0000 [thread overview]
Message-ID: <20080226143744.GA24332@fluff.org.uk> (raw)
In-Reply-To: <20080220193709.GD21139@uranus.ravnborg.org>
On Wed, Feb 20, 2008 at 08:37:09PM +0100, Sam Ravnborg wrote:
> On Wed, Feb 20, 2008 at 03:44:04PM +0100, Michael Buesch wrote:
> > On Wednesday 20 February 2008 01:44:38 Gordon Farquharson wrote:
> > > Hi Michael
> > >
> > > On Feb 19, 2008 3:41 AM, Michael Buesch <mb@bu3sch.de> wrote:
> > >
> > > > > [2] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=7492d4a416d68ab4bd254b36ffcc4e0138daa8ff
> > > > >
> > > >
> > > > That doesn't cause me to magically sign off this sort of patches, too.
> > > > The sanity check is clearly broken in file2alias.c, as it checks something
> > > > from the target kernel against the host environment it is compiled on.
> > > > That doesn't make any sense at all.
> > >
> > > I think that you make some good points, but I'm at a loss as to how to
> > > fix the problem. Do you have any suggestions?
> >
> > Remove the broken sanity check, if it's not possible the check there.
> The check is valid for > 99% of the kernel builds as
> cross compile builds are not that typical.
> And the check is there for the sake of modutils.
I build all of my ARM kernels on an x86 box, it is much faster
and I don't have to ensure I have a read/write capable filesystem
for any of my ARM boards.
--
Ben (ben@fluff.org, http://www.fluff.org/)
'a smiley only costs 4 bytes'
next prev parent reply other threads:[~2008-02-26 14:38 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 22:03 [RFC] [PATCH] Fix b43 driver build for arm Gordon Farquharson
2008-02-18 22:08 ` Michael Buesch
2008-02-18 22:13 ` Russell King
2008-02-18 22:24 ` Michael Buesch
2008-02-18 22:34 ` Russell King
2008-02-18 22:43 ` Michael Buesch
2008-02-18 22:50 ` Harvey Harrison
2008-02-18 22:56 ` Michael Buesch
2008-02-18 22:53 ` Russell King
2008-02-18 23:00 ` Russell King
2008-02-18 23:17 ` Michael Buesch
2008-02-18 23:42 ` Sam Ravnborg
2008-02-19 0:01 ` Michael Buesch
2008-02-19 4:59 ` Gordon Farquharson
2008-02-19 10:41 ` Michael Buesch
2008-02-20 0:44 ` Gordon Farquharson
2008-02-20 14:44 ` Michael Buesch
2008-02-20 19:37 ` Sam Ravnborg
2008-02-22 4:24 ` Gordon Farquharson
2008-02-22 12:08 ` Gordon Farquharson
2008-02-22 14:07 ` Michael Buesch
2008-02-23 4:34 ` Gordon Farquharson
2008-02-23 5:51 ` Michael Buesch
2008-02-23 10:14 ` Gordon Farquharson
2008-02-23 15:58 ` Michael Buesch
2008-02-26 14:37 ` Ben Dooks [this message]
2008-02-26 16:12 ` Gordon Farquharson
2008-02-19 5:32 ` Sam Ravnborg
2008-02-22 13:13 ` Matthieu CASTET
2008-02-18 23:04 ` Michael Buesch
2008-02-19 8:37 ` Geert Uytterhoeven
2008-02-19 10:34 ` Michael Buesch
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=20080226143744.GA24332@fluff.org.uk \
--to=ben-linux@fluff.org \
--cc=akpm@osdl.org \
--cc=gordonfarquharson@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=sam@ravnborg.org \
--cc=stefano.brivio@polimi.it \
--cc=torvalds@osdl.org \
--cc=viro@ftp.linux.org.uk \
/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.