linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build warning after merge of the mips tree
Date: Thu, 25 Aug 2011 09:18:37 +1000	[thread overview]
Message-ID: <20110825091837.ebf61e307d65fb77e29b2ca3@canb.auug.org.au> (raw)
In-Reply-To: <20110822104809.451b0e8d7b231d70d73aa256@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 649 bytes --]

Hi Ralf,

On Mon, 22 Aug 2011 10:48:09 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> On Sun, 21 Aug 2011 09:43:02 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > The mips tree today seems like a complete mess.  It seem to be some
> > historical tree including commits with commit dates going back to 1994
> > and v1.1.68!  Please fix it up as it is unusable in its current form.
> 
> Since it hasn't been fixed yet, I have reset the mips tree to be what it
> was in next-20110819.

Still not fixed :-(

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2011-08-24 23:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-20 23:43 linux-next: build warning after merge of the mips tree Stephen Rothwell
2011-08-22  0:48 ` Stephen Rothwell
2011-08-24 23:18   ` Stephen Rothwell [this message]
2020-07-29 10:31 Stephen Rothwell
2020-07-30  1:04 ` Jiaxun Yang
2020-07-30  1:40   ` Stephen Rothwell
2020-07-30  1:56     ` Jiaxun Yang
2020-07-30 22:39       ` 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=20110825091837.ebf61e307d65fb77e29b2ca3@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=ralf@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;
as well as URLs for NNTP newsgroup(s).