All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Wu Zhangjin <wuzhangjin@gmail.com>
Cc: zhangfx@lemote.com, yanh@lemote.com, huhb@lemote.com,
	Nicholas Mc Guire <hofrat@hofr.at>,
	Arnaud Patard <apatard@mandriva.com>,
	loongson-dev@googlegroups.com, linux-mips@linux-mips.org
Subject: Re: [PATCH v2 0/7] add support for lemote loongson2f machines
Date: Tue, 10 Nov 2009 12:22:27 +0100	[thread overview]
Message-ID: <20091110112226.GA18773@linux-mips.org> (raw)
In-Reply-To: <1257786384.14315.21.camel@falcon.domain.org>

On Tue, Nov 10, 2009 at 01:06:24AM +0800, Wu Zhangjin wrote:

> On Mon, 2009-11-09 at 17:54 +0100, Ralf Baechle wrote:
> > On Tue, Nov 10, 2009 at 12:36:48AM +0800, Wu Zhangjin wrote:
> > 
> > > > Grant Likely convinced me in Tokyo that this is the way to go.  He intends
> > > > to rewrite the FDT code into an easily re-usable library which he estimates
> > > > to take a month or two after which I'd like to start using it on MIPS.
> > > > This probably also means FDT support for PMON will eventually be needed.
> > > > 
> > > 
> > > Thanks for your pointer, Will take a look at FDT asap.
> > > 
> > > > Until then of course machtype=<whatever> is a fair solution.
> > > > 
> > > 
> > > are you ready to apply it? then I will push the Cpufreq and Standby
> > > support, and really hope we can get a full loongson2f support in the
> > > mainline's 33 version ;)
> > 
> > I had already taken the previous version into the -queue tree.
> > 
> > What are the changes since -v1?  I've done a few changes myself, mostly
> > tweaking the English language bits of the patch, so incremental patches
> > would be ideal.
> > 
> 
> Very few of changes, did you apply the changes in this one?

Sorry, I thought of your prior Loongson 2E series.

  Ralf

      reply	other threads:[~2009-11-10 11:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-09 16:05 [PATCH v2 0/7] add support for lemote loongson2f machines Wu Zhangjin
2009-11-09 16:06 ` [PATCH v2 1/7] [loongson] lemote-2f: add a LEMOTE_MACH2F kernel option Wu Zhangjin
2009-11-10 13:05   ` Ralf Baechle
2009-11-09 16:06 ` [PATCH v2 2/7] [loongson] lemote-2f: rtc: enable legacy RTC driver Wu Zhangjin
2009-11-10 13:06   ` Ralf Baechle
2009-11-09 16:06 ` [PATCH v2 3/7] [loongson] lemote-2f: add basic cs5536 vsm support Wu Zhangjin
2009-11-10 13:16   ` Ralf Baechle
2009-11-09 16:06 ` [PATCH v2 4/7] [loongson] lemote-2f: add pci support Wu Zhangjin
2009-11-10 13:06   ` Ralf Baechle
2009-11-09 16:06 ` [PATCH v2 5/7] [loongson] lemote-2f: add irq support Wu Zhangjin
2009-11-10 13:06   ` Ralf Baechle
2009-11-09 16:06 ` [PATCH v2 6/7] [loongson] lemote-2f: add reset support Wu Zhangjin
2009-11-10 13:07   ` Ralf Baechle
2009-11-09 16:06 ` [PATCH v2 7/7] [loongson] lemote-2f: add defconfig file Wu Zhangjin
2009-11-10 13:07   ` Ralf Baechle
2009-11-09 16:11 ` [PATCH v2 0/7] add support for lemote loongson2f machines Ralf Baechle
2009-11-09 16:36   ` Wu Zhangjin
2009-11-09 16:54     ` Ralf Baechle
2009-11-09 17:06       ` Wu Zhangjin
2009-11-10 11:22         ` Ralf Baechle [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=20091110112226.GA18773@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=apatard@mandriva.com \
    --cc=hofrat@hofr.at \
    --cc=huhb@lemote.com \
    --cc=linux-mips@linux-mips.org \
    --cc=loongson-dev@googlegroups.com \
    --cc=wuzhangjin@gmail.com \
    --cc=yanh@lemote.com \
    --cc=zhangfx@lemote.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.