From: Ralf Baechle <ralf@linux-mips.org>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: David Daney <ddaney@caviumnetworks.com>,
Dezhong Diao <dediao@cisco.com>,
devicetree-discuss@lists.ozlabs.org, linux-mips@linux-mips.org,
dvomlehn@cisco.com
Subject: Re: [PATCH v2 1/2] MIPS: Add device tree support to MIPS
Date: Wed, 28 Jul 2010 22:33:20 +0100 [thread overview]
Message-ID: <20100728213320.GA11538@linux-mips.org> (raw)
In-Reply-To: <AANLkTi=74zoQziQTmAGo-cNtF9FAT77h+KZagsNEFjEf@mail.gmail.com>
On Wed, Jul 28, 2010 at 01:25:52PM -0600, Grant Likely wrote:
> It would probably be best if I at least pick up the first patch into
> my test tree to give it a spin with the latest changes. I'd be happy
> to take the 2nd too to avoid ordering issues.
Makes sense and even though this patch applies to arch/mips it's probably
more of an DT than a MIPS patch.
That said a long standing problem is that code that is relevant to MIPS
tends to get tested only if it's in one of the MIPS trees but far less in
other trees such as -next.
Ralf
prev parent reply other threads:[~2010-07-28 21:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 21:49 [PATCH v2 1/2] MIPS: Add device tree support to MIPS Dezhong Diao
2010-07-27 21:49 ` Dezhong Diao
2010-07-28 18:54 ` Grant Likely
2010-07-28 18:54 ` Grant Likely
2010-07-28 19:19 ` David Daney
2010-07-28 19:25 ` Grant Likely
2010-07-28 19:25 ` Grant Likely
2010-07-28 20:47 ` Dezhong Diao (dediao)
2010-07-28 20:47 ` Dezhong Diao (dediao)
2010-07-29 19:40 ` Grant Likely
2010-07-29 19:40 ` Grant Likely
2010-08-16 20:42 ` Grant Likely
2010-08-16 20:42 ` Grant Likely
2010-08-17 3:40 ` Stephen Rothwell
2010-08-17 3:40 ` Stephen Rothwell
2010-08-17 3:40 ` Stephen Rothwell
2010-08-18 14:39 ` Ralf Baechle
2010-08-18 14:39 ` Ralf Baechle
2010-08-18 15:18 ` Stephen Rothwell
2010-08-18 15:18 ` Stephen Rothwell
2010-08-18 15:36 ` Ralf Baechle
2010-08-18 15:36 ` Ralf Baechle
2010-07-28 21:33 ` 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=20100728213320.GA11538@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=ddaney@caviumnetworks.com \
--cc=dediao@cisco.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dvomlehn@cisco.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-mips@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.