public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Will Deacon <will.deacon@arm.com>
Cc: Michal Simek <michal.simek@xilinx.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"monstr@monstr.eu" <monstr@monstr.eu>,
	Zach Pfeffer <zachp@xilinx.com>, Nathan Rossi <nrossi@xilinx.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Catalin Marinas <Catalin.Marinas@arm.com>,
	Nathan Rossi <nathan.rossi@xilinx.com>,
	Michal Marek <mmarek@suse.cz>,
	"linux-kbuild@vger.kernel.org" <linux-kbuild@vger.kernel.org>,
	arm@kernel.org
Subject: Re: [PATCH v2] kbuild: Create directory for target DTB
Date: Sun, 29 Mar 2015 13:57:31 -0700	[thread overview]
Message-ID: <20150329205731.GB13301@localhost> (raw)
In-Reply-To: <20150318132004.GC10863@arm.com>

On Wed, Mar 18, 2015 at 01:20:04PM +0000, Will Deacon wrote:
> On Wed, Mar 18, 2015 at 12:39:07PM +0000, Michal Simek wrote:
> > From: Nathan Rossi <nathan.rossi@xilinx.com>
> > 
> > When building specific DTBs out of the kernel tree the vendor subdirs
> > (boot/dts/<vendor>) are not created, ensure that they are before
> > building the DTB.
> > 
> > Signed-off-by: Nathan Rossi <nathan.rossi@xilinx.com>
> > Signed-off-by: Michal Simek <michal.simek@xilinx.com>
> > ---
> > 
> > Changes in v2:
> > - Use $(dir ${dtc-tmp}) instead of `dirname ${dtc-tmp}`
> >   Reported-by: Will Deacon <will.deacon@arm.com>
> 
> Looks ok to me, but no idea which tree this should go through. Maybe
> arm-soc?
> 
>   Acked-by: Will Deacon <will.deacon@arm.com>

Sure. Please resend with appropriate acks to arm@kernel.org and we can apply it.


-Olof


  reply	other threads:[~2015-03-29 20:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-18 12:39 [PATCH v2] kbuild: Create directory for target DTB Michal Simek
2015-03-18 13:20 ` Will Deacon
2015-03-29 20:57   ` Olof Johansson [this message]
2015-03-30 12:39     ` Michal Simek

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=20150329205731.GB13301@localhost \
    --to=olof@lixom.net \
    --cc=Catalin.Marinas@arm.com \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.simek@xilinx.com \
    --cc=mmarek@suse.cz \
    --cc=monstr@monstr.eu \
    --cc=nathan.rossi@xilinx.com \
    --cc=nrossi@xilinx.com \
    --cc=will.deacon@arm.com \
    --cc=zachp@xilinx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox