From: Michael Ellerman <michael@ellerman.id.au>
To: Dave Jones <davej@redhat.com>
Cc: trinity@vger.kernel.org
Subject: Re: [PATCH 1/4] Add support for cross building using CROSS_COMPILE
Date: Fri, 07 Jun 2013 16:44:49 +1000 [thread overview]
Message-ID: <1370587489.4996.1.camel@concordia> (raw)
In-Reply-To: <20130607053037.GB2888@redhat.com>
On Fri, 2013-06-07 at 01:30 -0400, Dave Jones wrote:
> On Fri, Jun 07, 2013 at 03:04:26PM +1000, Michael Ellerman wrote:
> > On Sat, Jun 01, 2013 at 09:46:15PM +1000, Michael Ellerman wrote:
> > > Similarly to the kernel. CROSS_COMPILE is optional, when specified it's
> > > a prefix, eg. myarch-linux-gnu-
> > >
> > > We still allow overriding CC, separately, or in addition to setting
> > > CROSS_COMPILE.
> > >
> > > There is also support for cross configuring, because at the moment all
> > > the configure tests only need to build, they're not run.
> >
> > Did this series make it to the list? They were the first I sent just
> > after I subscribed. Or did you just not like them ? :)
>
> Sorry, I just overlooked them.
No stress.
> > Anyway the .gitignore patch conflicts now, I can rebase and resend if
> > you like.
>
> All applied and pushed out.
>
> (For small 1-2 liners I don't mind fixing up git merges. Bigger stuff I'd I've
> asked for a rebase.)
Thanks.
cheers
prev parent reply other threads:[~2013-06-07 6:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-01 11:46 [PATCH 1/4] Add support for cross building using CROSS_COMPILE Michael Ellerman
2013-06-01 11:46 ` [PATCH 2/4] Ignore vim swap files Michael Ellerman
2013-06-01 11:46 ` [PATCH 3/4] Fix compile error in net/bpf.c for non x86 Michael Ellerman
2013-06-01 11:46 ` [PATCH 4/4] Sanity check the syscall number in print_syscall_name() Michael Ellerman
2013-06-07 5:04 ` [PATCH 1/4] Add support for cross building using CROSS_COMPILE Michael Ellerman
2013-06-07 5:30 ` Dave Jones
2013-06-07 6:44 ` Michael Ellerman [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=1370587489.4996.1.camel@concordia \
--to=michael@ellerman.id.au \
--cc=davej@redhat.com \
--cc=trinity@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