linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: balbi@ti.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: boot: dts: build keystone devicetree blob
Date: Fri, 21 Mar 2014 09:43:28 -0500	[thread overview]
Message-ID: <20140321144328.GC12310@saruman.home> (raw)
In-Reply-To: <532C4F40.5010903@ti.com>

On Fri, Mar 21, 2014 at 10:40:00AM -0400, Santosh Shilimkar wrote:
> On Wednesday 12 March 2014 12:35 PM, Santosh Shilimkar wrote:
> > On Wednesday 12 March 2014 11:48 PM, Felipe Balbi wrote:
> >> Currently, even when building keystone only
> >> kernel builds, DTB won't get build because
> >> we lack a Makefile rule to get it compiled.
> >>
> >> This patch adds that rule so mainline kernel
> >> users have a chance to use up-to-date DTB on
> >> keystone 2 platforms.
> >>
> >> Signed-off-by: Felipe Balbi <balbi@ti.com>
> >> ---
> >>
> > We have been building dtbs with explicit command
> > instead of dtbs since it was just one dtb so far
> > supported. Was planning to add the rule once more
> > boards get added. Now with Lamarr and Edision in
> > for next merge window, will do that post 3.15-rc1.
> > 
> Just to close the loop, I added a patch as part
> of my 3.15 fixes which builds all keystone dt
> blobs.

cool, thanks

-- 
balbi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140321/d622f2f6/attachment.sig>

  reply	other threads:[~2014-03-21 14:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-12 15:48 [PATCH] arm: boot: dts: build keystone devicetree blob Felipe Balbi
2014-03-12 16:35 ` Santosh Shilimkar
2014-03-12 16:53   ` Felipe Balbi
2014-03-21 14:40   ` Santosh Shilimkar
2014-03-21 14:43     ` Felipe Balbi [this message]
2014-03-25 13:21       ` Santosh Shilimkar

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=20140321144328.GC12310@saruman.home \
    --to=balbi@ti.com \
    --cc=linux-arm-kernel@lists.infradead.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).