All of lore.kernel.org
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio.salvador@ossystems.com.br>
To: Ting Liu <ting.liu@nxp.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [meta-freescale-layer][PATCH 00/50] QorIQ patches
Date: Fri, 5 Aug 2016 10:11:02 -0300	[thread overview]
Message-ID: <CAP9ODKrLo5uHBtQPzHfAvLVET6LXvOSMeKw3j+Dg5KK-GmRRdw@mail.gmail.com> (raw)
In-Reply-To: <DB5PR0401MB17827B9209047A29AB11481299180@DB5PR0401MB1782.eurprd04.prod.outlook.com>

On Fri, Aug 5, 2016 at 2:56 AM, Ting Liu <ting.liu@nxp.com> wrote:
>> -----Original Message-----
>> From: Otavio Salvador [mailto:otavio.salvador@ossystems.com.br]
>> Sent: Thursday, August 04, 2016 10:47 PM
>> To: Ting Liu <ting.liu@nxp.com>
>> Cc: Zhenhua Luo <zhenhua.luo@nxp.com>; meta-
>> freescale@yoctoproject.org
>> Subject: Re: [meta-freescale] [meta-freescale-layer][PATCH 00/50] QorIQ
>> patches
>>
>> On Mon, Aug 1, 2016 at 11:46 AM, Ting Liu <ting.liu@nxp.com> wrote:
>> > Hello Otavio,
>> >
>> >> -----Original Message-----
>> >> From: Otavio Salvador [mailto:otavio.salvador@ossystems.com.br]
>> >> Sent: Monday, August 01, 2016 9:53 PM
>> >> To: Zhenhua Luo <zhenhua.luo@nxp.com>
>> >> Cc: Ting Liu <ting.liu@nxp.com>; meta-freescale@yoctoproject.org
>> >> Subject: Re: [meta-freescale] [meta-freescale-layer][PATCH 00/50]
>> >> QorIQ patches
>> >>
>> >> On Mon, Aug 1, 2016 at 7:08 AM, Zhenhua Luo <zhenhua.luo@nxp.com>
>> >> wrote:
>> >> > Can you please review and merge the remaining patches of QorIQ SDK
>> 2.0?
>> >> Currently the kernel build is blocked for QorIQ targets. Attached is
>> >> the latest CI report.
>> >>
>> >> I merged a number of changes since you made the branch and to be
>> >> honest I assumed they were the same stuff; please rebase the tree and
>> >> let me know when it is ready for review again please.
>> > [Liu Ting-B28495] I did not see new commits on github meta-freescale layer
>> since Jul 22.
>> > The tree I sent on July 23 was already based on the latest.
>>
>> I sent the patches I think are fine to master-next; the device tree path
>> changes seems unclear for me. Why it is need?
>
> [Liu Ting-B28495] a sub-folder fsl/ under arch/powerpc/boot/dts/ was created to hold all the device tree files in kernel source:
> http://git.freescale.com/git/cgit.cgi/ppc/sdk/linux.git/tree/arch/powerpc/boot/dts/fsl?h=sdk-v2.0.x

The path for the dtb is not the usual way of using it; it would be
better if the Makefile was fixed so normal usage works.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750


  reply	other threads:[~2016-08-05 13:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-01 10:08 [meta-freescale-layer][PATCH 00/50] QorIQ patches Zhenhua Luo
2016-08-01 13:53 ` Otavio Salvador
2016-08-01 14:46   ` Ting Liu
2016-08-01 15:02     ` Otavio Salvador
2016-08-01 16:36       ` Bob Cochran
2016-08-02  9:40         ` Zhenhua Luo
2016-08-04 14:46     ` Otavio Salvador
2016-08-05  5:56       ` Ting Liu
2016-08-05 13:11         ` Otavio Salvador [this message]
2016-08-08  3:15           ` Zhenhua Luo
2016-08-08 10:24             ` Otavio Salvador
2016-08-08 11:05               ` Zhenhua Luo
2016-08-09 15:56                 ` Otavio Salvador
2016-08-10 16:06                   ` Ting Liu
2016-08-10 17:27                     ` Otavio Salvador
2016-08-11 14:52       ` Ting Liu
2016-08-11 16:11         ` Otavio Salvador
  -- strict thread matches above, loose matches on Subject: below --
2016-07-23 15:09 ting.liu
2016-07-23 15:13 ` Ting Liu
2016-07-25  3:56   ` Robert E. Cochran

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=CAP9ODKrLo5uHBtQPzHfAvLVET6LXvOSMeKw3j+Dg5KK-GmRRdw@mail.gmail.com \
    --to=otavio.salvador@ossystems.com.br \
    --cc=meta-freescale@yoctoproject.org \
    --cc=ting.liu@nxp.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 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.