All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Wanlong Gao <wanlong.gao@gmail.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Michael Ellerman <michael@ellerman.id.au>,
	Linux Kernel Development <linux-kernel@vger.kernel.org>,
	Linux-Next <linux-next@vger.kernel.org>
Subject: Re: Build regressions/improvements in v3.0-rc3
Date: Wed, 15 Jun 2011 17:37:53 +0100	[thread overview]
Message-ID: <20110615163753.GA15155@linux-mips.org> (raw)
In-Reply-To: <20110615222932.05a863fc.sfr@canb.auug.org.au>

On Wed, Jun 15, 2011 at 10:29:32PM +1000, Stephen Rothwell wrote:

> On Wed, 15 Jun 2011 19:44:41 +0800 Wanlong Gao <wanlong.gao@gmail.com> wrote:
> >
> > <snip>
> > I see that some mips fixes in ralf's tree but not been pulled. almost
> > for about one month.
> 
> Well, the mips tree in linux-next is
> git://git.linux-mips.org/pub/scm/upstream-sfr.git#mips-for-linux-next and
> I fetch it every day.

I only have the new bits in linux-next but not the pending for the current
work-in-progress kernel, that is 3.0.  Those are queued in

http://git.linux-mips.org/?p=upstream-linus.git;a=summary
git://git.linux-mips.org/pub/scm/upstream-linus.git

and I've sent two pull requests to Linus so far which went without
reaction ...

  Ralf

  reply	other threads:[~2011-06-15 16:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-15 11:44 re:Build regressions/improvements in v3.0-rc3 Wanlong Gao
2011-06-15 12:29 ` Build " Stephen Rothwell
2011-06-15 16:37   ` Ralf Baechle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-06-15 16:59 Wanlong Gao
2011-06-15 16:59 ` Wanlong Gao
2011-06-15  9:11 Geert Uytterhoeven
2011-06-15  9:19 ` Geert Uytterhoeven
2011-06-18  8:30   ` Stephen Rothwell
2011-06-18 12:19     ` Geert Uytterhoeven
2011-06-23 11:27     ` Stephen Rothwell
2011-06-24  6:08       ` Geert Uytterhoeven
2011-06-24  6:10         ` Stephen Rothwell
2011-06-24 14:50           ` Geert Uytterhoeven
2011-06-15 12:03 ` Tomas Winkler
2011-06-15 12:41 ` Stephen Rothwell
2011-06-15 13:11   ` Geert Uytterhoeven
2011-06-15 13:22     ` Stephen Rothwell

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=20110615163753.GA15155@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=michael@ellerman.id.au \
    --cc=sfr@canb.auug.org.au \
    --cc=wanlong.gao@gmail.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 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.