Linux-Next discussions
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: sfr@canb.auug.org.au
Cc: linux-next@vger.kernel.org, tony@bakeyournoodle.com
Subject: Re: sparc32 build...
Date: Thu, 15 Mar 2012 20:13:23 -0700 (PDT)	[thread overview]
Message-ID: <20120315.201323.500647975902683335.davem@davemloft.net> (raw)
In-Reply-To: <20120316141222.210a0ccf1a245367e5c956f5@canb.auug.org.au>

From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Fri, 16 Mar 2012 14:12:22 +1100

> Hi Dave,
> 
> On Thu, 15 Mar 2012 19:59:34 -0700 (PDT) David Miller <davem@davemloft.net> wrote:
>>
>> Stephen, just checking, did my Makefile change make the sparc32 build
>> failures go away with newer tools?
> 
> Yeah, seems to have worked.  See (sparc defconfig builds)
> http://kisskb.ellerman.id.au/kisskb/buildresult/5869567/ (next-20120313 -
> bad) v. http://kisskb.ellerman.id.au/kisskb/buildresult/5871624/
> (next-20120314 - good)

Awesome, thanks.

      reply	other threads:[~2012-03-16  3:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-16  2:59 sparc32 build David Miller
2012-03-16  3:12 ` Stephen Rothwell
2012-03-16  3:13   ` David Miller [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=20120315.201323.500647975902683335.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tony@bakeyournoodle.com \
    /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