All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: David Daney <ddaney@caviumnetworks.com>,
	Ralf Baechle <ralf@linux-mips.org>,
	Yoichi Yuasa <yuasa@linux-mips.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: Wed, 18 Jul 2012 21:07:38 +0000	[thread overview]
Message-ID: <20120718140738.ca6f8f5a.akpm@linux-foundation.org> (raw)
In-Reply-To: <CAMuHMdWW=sAff-iw0EiHaejr34Z4u_X7w3nHf6Tfo-c2f=Qijg@mail.gmail.com>

On Wed, 18 Jul 2012 10:35:46 +0200
Geert Uytterhoeven <geert@linux-m68k.org> wrote:

> On Mon, Jul 16, 2012 at 9:27 PM, Geert Uytterhoeven
> <geert@linux-m68k.org> wrote:
> > On Fri, Jun 22, 2012 at 7:54 PM, David Daney <ddaney@caviumnetworks.com> wrote:
> >> 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.
> >
> > It's also desperately needed in mainline for 3.5.
> >
> > Ralf?
> 
> Andrew? This prevents any green MIPS builds.
> 

The patch is already in linux-next via Ralf's tree.

Perhaps he nodded off - I'll send it at Linus right now.

WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: David Daney <ddaney@caviumnetworks.com>,
	Ralf Baechle <ralf@linux-mips.org>,
	Yoichi Yuasa <yuasa@linux-mips.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: Wed, 18 Jul 2012 14:07:38 -0700	[thread overview]
Message-ID: <20120718140738.ca6f8f5a.akpm@linux-foundation.org> (raw)
In-Reply-To: <CAMuHMdWW=sAff-iw0EiHaejr34Z4u_X7w3nHf6Tfo-c2f=Qijg@mail.gmail.com>

On Wed, 18 Jul 2012 10:35:46 +0200
Geert Uytterhoeven <geert@linux-m68k.org> wrote:

> On Mon, Jul 16, 2012 at 9:27 PM, Geert Uytterhoeven
> <geert@linux-m68k.org> wrote:
> > On Fri, Jun 22, 2012 at 7:54 PM, David Daney <ddaney@caviumnetworks.com> wrote:
> >> 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.
> >
> > It's also desperately needed in mainline for 3.5.
> >
> > Ralf?
> 
> Andrew? This prevents any green MIPS builds.
> 

The patch is already in linux-next via Ralf's tree.

Perhaps he nodded off - I'll send it at Linus right now.

WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux MIPS Mailing List <linux-mips@linux-mips.org>,
	Linux-sh list <linux-sh@vger.kernel.org>,
	linux-kernel@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>,
	David Daney <ddaney@caviumnetworks.com>,
	Linuxppc-dev <linuxppc-dev@ozlabs.org>,
	Paul Mundt <lethal@linux-sh.org>, Chris Zankel <chris@zankel.net>,
	Yoichi Yuasa <yuasa@linux-mips.org>
Subject: Re: [PATCH] MIPS: fix bug.h MIPS build regression
Date: Wed, 18 Jul 2012 14:07:38 -0700	[thread overview]
Message-ID: <20120718140738.ca6f8f5a.akpm@linux-foundation.org> (raw)
In-Reply-To: <CAMuHMdWW=sAff-iw0EiHaejr34Z4u_X7w3nHf6Tfo-c2f=Qijg@mail.gmail.com>

On Wed, 18 Jul 2012 10:35:46 +0200
Geert Uytterhoeven <geert@linux-m68k.org> wrote:

> On Mon, Jul 16, 2012 at 9:27 PM, Geert Uytterhoeven
> <geert@linux-m68k.org> wrote:
> > On Fri, Jun 22, 2012 at 7:54 PM, David Daney <ddaney@caviumnetworks.com> wrote:
> >> 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.
> >
> > It's also desperately needed in mainline for 3.5.
> >
> > Ralf?
> 
> Andrew? This prevents any green MIPS builds.
> 

The patch is already in linux-next via Ralf's tree.

Perhaps he nodded off - I'll send it at Linus right now.

  reply	other threads:[~2012-07-18 21:07 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-17 19:46 Build regressions/improvements in v3.5-rc3 Geert Uytterhoeven
2012-06-17 19:56 ` Geert Uytterhoeven
2012-06-17 19:56   ` Geert Uytterhoeven
2012-06-17 19:56   ` Geert Uytterhoeven
2012-06-17 21:53   ` Benjamin Herrenschmidt
2012-06-17 21:53     ` Benjamin Herrenschmidt
2012-06-17 21:53     ` Benjamin Herrenschmidt
2012-06-17 22:30     ` Andreas Schwab
2012-06-17 22:30       ` Andreas Schwab
2012-06-17 22:30       ` Andreas Schwab
2012-06-18 20:27   ` Kim Phillips
2012-06-18 20:27     ` Kim Phillips
2012-06-18 20:35     ` Mauro Carvalho Chehab
2012-06-18 20:35       ` Mauro Carvalho Chehab
2012-06-20  3:59   ` Paul Mundt
2012-06-20  3:59     ` Paul Mundt
2012-06-20  3:59     ` Paul Mundt
2012-06-20  8:02     ` Geert Uytterhoeven
2012-06-20  8:02       ` Geert Uytterhoeven
2012-06-20  8:02       ` Geert Uytterhoeven
2012-06-20 12:50     ` Giuseppe CAVALLARO
2012-06-20 12:50       ` Giuseppe CAVALLARO
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  6:27     ` Yoichi Yuasa
2012-06-20  6:27     ` Yoichi Yuasa
2012-06-20  7:09     ` John Crispin
2012-06-20  7:09       ` John Crispin
2012-06-20  7:09       ` John Crispin
2012-06-20 10:40     ` Sergei Shtylyov
2012-06-20 10:40       ` Sergei Shtylyov
2012-06-20 10:40       ` Sergei Shtylyov
2012-06-20 16:12     ` Ralf Baechle
2012-06-20 16:12       ` Ralf Baechle
2012-06-20 16:12       ` Ralf Baechle
2012-06-22 17:54       ` David Daney
2012-06-22 17:54         ` David Daney
2012-06-22 17:54         ` David Daney
2012-06-22 17:54         ` David Daney
2012-07-16 19:27         ` Geert Uytterhoeven
2012-07-16 19:27           ` Geert Uytterhoeven
2012-07-16 19:27           ` Geert Uytterhoeven
2012-07-18  8:35           ` Geert Uytterhoeven
2012-07-18  8:35             ` Geert Uytterhoeven
2012-07-18  8:35             ` Geert Uytterhoeven
2012-07-18 21:07             ` Andrew Morton [this message]
2012-07-18 21:07               ` Andrew Morton
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=20120718140738.ca6f8f5a.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=chris@zankel.net \
    --cc=ddaney@caviumnetworks.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.