From: Michael Buesch <mb@bu3sch.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
David Miller <davem@davemloft.net>,
gordonfarquharson@gmail.com, netdev@vger.kernel.org,
linux-wireless@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: pull request: wireless-2.6 2008-02-27
Date: Sat, 1 Mar 2008 00:13:11 +0100 [thread overview]
Message-ID: <200803010013.11458.mb@bu3sch.de> (raw)
In-Reply-To: <1204302853.3938.40.camel@johannes.berg>
On Friday 29 February 2008 17:34:13 Johannes Berg wrote:
>
> On Fri, 2008-02-29 at 11:26 -0500, John W. Linville wrote:
> > On Fri, Feb 29, 2008 at 01:16:59PM +0100, Michael Buesch wrote:
> >
> > > I'm wondering if we can't simply pass a commandline parameter to file2alias
> > > that tells it whether we are crosscompiling. It should simply omit the sanity check
> >
> > Sounds reasonable to me.
>
> In fact, file2alias shouldn't need a command line argument ...
Well, if...
> > > in that case. Is there any easy and reliable way to find out whether we
> > > are crosscompiling from a makefile (I don't know the makefile core that much)?
> >
> > Non-empty CROSS_COMPILE definition?
>
> ... it can just check whether CROSS_COMPILE is set in its environment.
> No?
Is that exported to the environment?
--
Greetings Michael.
next prev parent reply other threads:[~2008-02-29 23:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 1:41 pull request: wireless-2.6 2008-02-27 John W. Linville
2008-02-28 7:51 ` David Miller
2008-02-28 14:51 ` pull request: wireless-2.6 2008-02-28 John W. Linville
2008-02-28 19:22 ` David Miller
2008-02-28 21:21 ` pull request: wireless-2.6 2008-02-27 Gordon Farquharson
2008-02-28 21:30 ` David Miller
2008-02-28 23:56 ` Gordon Farquharson
2008-02-29 0:15 ` David Miller
2008-02-29 12:16 ` Michael Buesch
2008-02-29 16:26 ` John W. Linville
2008-02-29 16:34 ` Johannes Berg
2008-02-29 19:10 ` John W. Linville
2008-02-29 19:54 ` Johannes Berg
2008-02-29 21:42 ` John W. Linville
2008-03-01 13:01 ` Sam Ravnborg
2008-03-01 15:51 ` Michael Buesch
2008-03-02 11:58 ` Sam Ravnborg
2008-03-02 20:00 ` Gordon Farquharson
2008-03-02 20:25 ` Michael Buesch
2008-03-18 4:07 ` Gordon Farquharson
2008-03-23 20:51 ` Sam Ravnborg
2008-03-23 21:23 ` Gordon Farquharson
2008-03-01 22:59 ` David Miller
2008-03-02 15:44 ` Adrian Bunk
2008-02-29 23:13 ` Michael Buesch [this message]
2008-02-29 23:51 ` Randy Dunlap
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=200803010013.11458.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=gordonfarquharson@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).