Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Gabor Juhos <juhosg@openwrt.org>
To: John Crispin <john@phrozen.org>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH 3/6] DT: MIPS: ralink: extend RT3050 dtsi and dts file
Date: Sun, 14 Apr 2013 11:50:16 +0200	[thread overview]
Message-ID: <516A7BD8.2090505@openwrt.org> (raw)
In-Reply-To: <51699CEB.9000806@phrozen.org>

2013.04.13. 19:59 keltezéssel, John Crispin írta:
> 
>>> * remove nodes for cores whose drivers are not upstream yet
>>
>>    And you call that "extend"? :-)
> 
> 
> ermm yes, lets change it to "clean up"  :)

When you are going to change that, please remove the #{address,size}-cells
properties from the root node in the rt3052_eval.dts file. The rt3050.dtsi file
contains those properties with the same values already.

-Gabor

  reply	other threads:[~2013-04-14  9:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-13  8:50 [PATCH 1/6] DT: add vendor prefixes for Ralink John Crispin
2013-04-13  8:50 ` [PATCH 2/6] DT: add documentation for the Ralink MIPS SoCs John Crispin
2013-04-14  9:44   ` Gabor Juhos
2013-04-13  8:50 ` [PATCH 3/6] DT: MIPS: ralink: extend RT3050 dtsi and dts file John Crispin
2013-04-13 14:49   ` Sergei Shtylyov
2013-04-13 17:59     ` John Crispin
2013-04-14  9:50       ` Gabor Juhos [this message]
2013-04-13  8:50 ` [PATCH 4/6] DT: MIPS: ralink: add RT2880 dts files John Crispin
2013-04-14  9:53   ` Gabor Juhos
2013-08-23 18:34   ` Sergei Shtylyov
2013-08-23 18:37     ` Sergei Shtylyov
2013-08-23 18:44     ` David Daney
2013-04-13  8:50 ` [PATCH 5/6] DT: MIPS: ralink: add RT3883 " John Crispin
2013-04-14  9:54   ` Gabor Juhos
2013-04-13  8:50 ` [PATCH 6/6] DT: MIPS: ralink: add MT7620 " John Crispin
2013-04-14 11:41   ` Gabor Juhos

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=516A7BD8.2090505@openwrt.org \
    --to=juhosg@openwrt.org \
    --cc=john@phrozen.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox