devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
	Nicolas.Pitre.nicolas.pitre-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
	Lee Jones <lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
	Grant.Likely.grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH] mach-ux500: add devicetree compat nodes
Date: Fri, 11 Nov 2011 18:00:10 +0100	[thread overview]
Message-ID: <CACRpkdb6n2mRWohGrv1d0VFLRsTMDPDzow7UY6jw=9rdt-ZkqA@mail.gmail.com> (raw)
In-Reply-To: <4EBD4F79.90302-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

On Fri, Nov 11, 2011 at 5:38 PM, Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> [Me]
>> In that case we should hold this patch off and only keep it for
>> internal testing until all necessary drivers are ready and patched
>> so we can replace all board files with a single DT-based one,
>> instead of this compromise solution.
>>
> I would not hold off. You only need to have a minimal set that's enough
> to boot.

In our case UART, I2C and MMC is necessary to boot, so then we
anyway need to wait for these to be patched first. So we'd better hold
it back for now I think.

Linus Walleij

  parent reply	other threads:[~2011-11-11 17:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-11 15:05 [PATCH] mach-ux500: add devicetree compat nodes Niklas Hernaeus
     [not found] ` <1321023902-18870-1-git-send-email-niklas.hernaeus-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2011-11-11 15:17   ` Rob Herring
     [not found]     ` <4EBD3C85.1010508-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-11-11 15:59       ` Linus Walleij
     [not found]         ` <CACRpkda-9OVP8E1qO3Nc5znw_v7cKFiv8T5HHwTCnY2C9Fg7iA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-11-11 16:13           ` Rob Herring
     [not found]             ` <4EBD49A6.2020306-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-11-11 16:26               ` Linus Walleij
     [not found]                 ` <CACRpkdZrWW2jUYC0P7yY322YMdn9+4_NaGPhKtpGwR+e=F6+0A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-11-11 16:38                   ` Rob Herring
     [not found]                     ` <4EBD4F79.90302-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-11-11 17:00                       ` Linus Walleij [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-11-11 15:17 Niklas Hernaeus

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='CACRpkdb6n2mRWohGrv1d0VFLRsTMDPDzow7UY6jw=9rdt-ZkqA@mail.gmail.com' \
    --to=linus.walleij-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
    --cc=Grant.Likely.grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org \
    --cc=Nicolas.Pitre.nicolas.pitre-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).