From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] Set CROSS to $(CROSS_COMPILE) by default
Date: Sun, 29 Jan 2006 16:28:54 +0000 [thread overview]
Message-ID: <20060129162853.GB23189@vrfy.org> (raw)
In-Reply-To: <C5BA91F04186584EB68FD42BB4993E6B9D1248@FRQWOLEX01.frequentis.frq>
On Fri, Jan 27, 2006 at 05:23:46PM +0100, KRONSTORFER Horst wrote:
>
> > -----Original Message-----
> > From: Kay Sievers [mailto:kay.sievers@vrfy.org]
> > Sent: Freitag, 27. Jänner 2006 17:18
> > To: KRONSTORFER Horst
> > Cc: linux-hotplug-devel@lists.sourceforge.net
> > Subject: Re: [PATCH] Set CROSS to $(CROSS_COMPILE) by default
> >
> > On Fri, Jan 27, 2006 at 02:47:50PM +0100, KRONSTORFER Horst wrote:
> > > the following patch makes cross-compiling udev a little bit easier.
> >
> > > -CROSS > > > +CROSS = $(CROSS_COMPILE)
> >
> > CROSS_COMPILE seems more common that CROSS, right? The kernel
> > uses it too, so we can replace the CROSS entirely by CROSS_COMPILE?
>
> yes. just wanted to make the patch as noiseless as possible ;-)
Ok, fine, I just changed it to CROSS_COMPILE.
Thanks,
Kay
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2006-01-29 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-27 13:47 [PATCH] Set CROSS to $(CROSS_COMPILE) by default KRONSTORFER Horst
2006-01-27 16:17 ` Kay Sievers
2006-01-27 16:23 ` KRONSTORFER Horst
2006-01-29 16:28 ` Kay Sievers [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=20060129162853.GB23189@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@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).