linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: Robin Murphy <robin.murphy@arm.com>
Cc: linux-rockchip@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 0/4] NanoPC-T4 (and a bit of NanoPi M4) support
Date: Thu, 17 Jan 2019 15:01:36 +0100	[thread overview]
Message-ID: <21515619.cB86tSjWlH@phil> (raw)
In-Reply-To: <cover.1547466003.git.robin.murphy@arm.com>

Am Montag, 14. Januar 2019, 13:05:30 CET schrieb Robin Murphy:
> Hi all,
> 
> With the initial patch now queued (thankfully solving the version-number
> conundrum), here's an updated v2 of my further changes with the tweaks
> Heiko pointed out. Comparing GRF dumps didn't give any insight into the
> SD card thing, so I've kept the GPIO patch; ~100 interrupts per insertion
> is still more useful than 0!
> 
> Robin.
> 
> 
> Robin Murphy (4):
>   arm64: dts: rockchip: Add DT for NanoPi M4
>   arm64: dts: rockchip: Refine nanopi4 differences
>   arm64: dts: rockchip: Add NanoPC-T4 IR receiver
>   arm64: dts: rockchip: 'Fix' nanopi4 uSD card detect

queued all 4 for 5.1

Thanks
Heiko



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

      parent reply	other threads:[~2019-01-17 14:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-14 12:05 [PATCH v2 0/4] NanoPC-T4 (and a bit of NanoPi M4) support Robin Murphy
2019-01-14 12:05 ` [PATCH v2 1/4] arm64: dts: rockchip: Add DT for NanoPi M4 Robin Murphy
2019-01-16 21:12   ` Rob Herring
2019-01-14 12:05 ` [PATCH v2 2/4] arm64: dts: rockchip: Refine nanopi4 differences Robin Murphy
2019-01-14 12:05 ` [PATCH v2 3/4] arm64: dts: rockchip: Add NanoPC-T4 IR receiver Robin Murphy
2019-01-14 12:05 ` [PATCH v2 4/4] arm64: dts: rockchip: 'Fix' nanopi4 uSD card detect Robin Murphy
2019-01-17 14:01 ` Heiko Stuebner [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=21515619.cB86tSjWlH@phil \
    --to=heiko@sntech.de \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=robin.murphy@arm.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;
as well as URLs for NNTP newsgroup(s).