Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: David Daney <ddaney@caviumnetworks.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Yoichi Yuasa <yuasa@linux-mips.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Paul Mundt <lethal@linux-sh.org>, <linux-kernel@vger.kernel.org>,
	Linuxppc-dev <linuxppc-dev@ozlabs.org>,
	Linux MIPS Mailing List <linux-mips@linux-mips.org>,
	Linux-sh list <linux-sh@vger.kernel.org>,
	Chris Zankel <chris@zankel.net>
Subject: Re: [PATCH] MIPS: fix bug.h MIPS build regression
Date: Fri, 22 Jun 2012 10:54:06 -0700	[thread overview]
Message-ID: <4FE4B13E.10709@caviumnetworks.com> (raw)
In-Reply-To: <20120620161249.GB29196@linux-mips.org>

On 06/20/2012 09:12 AM, Ralf Baechle wrote:
> On Wed, Jun 20, 2012 at 03:27:59PM +0900, Yoichi Yuasa wrote:
>
>> Commit: 3777808873b0c49c5cf27e44c948dfb02675d578 breaks all MIPS builds.
>
> Thanks, fix applied.
>

Where was it applied?

It doesn't show up in linux-next for 20120622, which is where it is needed.

David Daney

WARNING: multiple messages have this Message-ID (diff)
From: David Daney <ddaney@caviumnetworks.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Yoichi Yuasa <yuasa@linux-mips.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Paul Mundt <lethal@linux-sh.org>,
	linux-kernel@vger.kernel.org,
	Linuxppc-dev <linuxppc-dev@ozlabs.org>,
	Linux MIPS Mailing List <linux-mips@linux-mips.org>,
	Linux-sh list <linux-sh@vger.kernel.org>,
	Chris Zankel <chris@zankel.net>
Subject: Re: [PATCH] MIPS: fix bug.h MIPS build regression
Date: Fri, 22 Jun 2012 10:54:06 -0700	[thread overview]
Message-ID: <4FE4B13E.10709@caviumnetworks.com> (raw)
Message-ID: <20120622175406.OcqwUGdge4JvwNKJo5X9LVkEICetqDNYyQrfBqzrQ1o@z> (raw)
In-Reply-To: <20120620161249.GB29196@linux-mips.org>

On 06/20/2012 09:12 AM, Ralf Baechle wrote:
> On Wed, Jun 20, 2012 at 03:27:59PM +0900, Yoichi Yuasa wrote:
>
>> Commit: 3777808873b0c49c5cf27e44c948dfb02675d578 breaks all MIPS builds.
>
> Thanks, fix applied.
>

Where was it applied?

It doesn't show up in linux-next for 20120622, which is where it is needed.

David Daney

  reply	other threads:[~2012-06-22 17:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1339962373-3224-1-git-send-email-geert@linux-m68k.org>
2012-06-17 19:56 ` Build regressions/improvements in v3.5-rc3 Geert Uytterhoeven
2012-06-17 21:53   ` Benjamin Herrenschmidt
2012-06-17 22:30     ` Andreas Schwab
2012-06-20  3:59   ` Paul Mundt
2012-06-20  8:02     ` Geert Uytterhoeven
2012-06-20 12:50     ` Giuseppe CAVALLARO
2012-06-20  6:27   ` [PATCH] MIPS: fix bug.h MIPS build regression Yoichi Yuasa
2012-06-20  7:09     ` John Crispin
2012-06-20 10:40     ` Sergei Shtylyov
2012-06-20 16:12     ` Ralf Baechle
2012-06-22 17:54       ` David Daney [this message]
2012-06-22 17:54         ` David Daney
2012-07-16 19:27         ` Geert Uytterhoeven
2012-07-18  8:35           ` Geert Uytterhoeven
2012-07-18 21:07             ` Andrew Morton

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=4FE4B13E.10709@caviumnetworks.com \
    --to=ddaney@caviumnetworks.com \
    --cc=chris@zankel.net \
    --cc=geert@linux-m68k.org \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=ralf@linux-mips.org \
    --cc=yuasa@linux-mips.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