public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: arm@kernel.org, Haojian Zhuang <haojian.zhuang@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	Daniel Mack <zonque@gmail.com>
Subject: Re: [GIT PULL] pxa-dt for v4.21
Date: Tue, 11 Dec 2018 07:49:59 -0800	[thread overview]
Message-ID: <20181211154959.ajujauw2ddbjdgif@localhost> (raw)
In-Reply-To: <87r2exu3wm.fsf@belgarion.home>

On Tue, Dec 04, 2018 at 08:50:17AM +0100, Robert Jarzmik wrote:
> Hi Arnd, Kevin, and Olof,
> 
> This is a pxa pull request for 4.21 device-tree. Please consider pulling.
> 
> The following changes since commit 651022382c7f8da46cb4872a545ee1da6d097d2a:
> 
>   Linux 4.20-rc1 (2018-11-04 15:37:52 -0800)
> 
> are available in the git repository at:
> 
>   https://github.com/rjarzmik/linux.git tags/pxa-dt-4.21
> 
> for you to fetch changes up to ad8044f87c0b53ee45f5d367584eefb222a06883:
> 
>   ARM: dts: pxa3xx: Add Raumfeld DTS files (2018-12-03 22:51:01 +0100)
> 
> ----------------------------------------------------------------
> This device-tree pxa update brings :
>  - various fixes from Daniel (W=12 issues mainly)
>  - support for the first pxa3xx devicetree pxa board

Very nice to see this conversion, and yay for having upstream support
for one more set of consumer products!

In general it could have been nice to see a bit of an overview of what
the new boards are for (what kind of product, and why they're split up
on separate DTS files with relatively small differences).

Merged into next/dt.



-Olof

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2018-12-11 16:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-04  7:50 [GIT PULL] pxa-dt for v4.21 Robert Jarzmik
2018-12-11 15:49 ` Olof Johansson [this message]

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=20181211154959.ajujauw2ddbjdgif@localhost \
    --to=olof@lixom.net \
    --cc=arm@kernel.org \
    --cc=haojian.zhuang@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=robert.jarzmik@free.fr \
    --cc=zonque@gmail.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