public inbox for linux-rockchip@lists.infradead.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
To: David Summers
	<beagleboard-8lkWs+DogrrqRUWtDFdff/XRex20P6io@public.gmane.org>
Cc: linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH v4 0/2] Reworked rk3288-tinker-s devicetree
Date: Mon, 08 Oct 2018 11:32:28 +0200	[thread overview]
Message-ID: <1701725.aGruVrenYc@phil> (raw)
In-Reply-To: <5dc8cdc9-20d5-bafa-3693-67ec09577234-8lkWs+DogrrqRUWtDFdff/XRex20P6io@public.gmane.org>

Hi David,

Am Samstag, 6. Oktober 2018, 14:54:37 CEST schrieb David Summers:
> Hi Heiko,
> 
> Re: 
> http://lists.infradead.org/pipermail/linux-rockchip/2018-September/021762.html
> 
> We've just had another use on Arm Arch interested in installing on a 
> Tinker Board. So this gives the chance to test the wi-fi patch on a 
> Tinker Board as well as Tinker Board S; so give better of where to apply 
> the patch.
> 
> So half thinking of having another go at the wi-fi patch.
> 
> But should first check, what problems did you see with the patch? Let me 
> know and I'll see if I can incorporate in patch update. As much as 
> anything, I want to minimize the number of tb{s}.dtb that I send out to 
> arch arm users, as testing before submission. E.g. the users have 
> limited tolerance, may be able to try a few device trees with them - but 
> if it takes too many iterations, they will just switch to linarno kernel ...

I did seem to have procrastinated a bit with my reply there, sorry
about that. I've replied to the original patch now.

Heiko


> 
> Ta,
> 
> David.
> 
> On 23/09/2018 12:38, Heiko Stuebner wrote:
> > Hi David,
> >
> > I've adpated your patches 1+2 like so and would like to add them this way
> > later on. Biggest change is of course making patch 1 solely about moving
> > the shared parts to the dtsi and adding the tinker-s.dts including the
> > emmc in the second patch.
> >
> > Apart from that you can also see some previously missing style-related
> > fixes. For example patch subject lines are somewhat specific, to allow
> > people browsing the git history to realize the core patch contents just
> > from the "headline" and also use the "correct" prefixes which vary
> > depending on the subsystem your changing.
> >
> > For future patches you can just do a "git log --oneline arch/arm/boot/dts"
> > (change directory depending on location of the change of course), to
> > see that arm32 dts use "ARM: dts: $soc-vendor: foo".
> >
> >
> > Also providing a commit message describing the individual change
> > in a bit more detail is important.
> >
> > The wifi patch is a different issue, so I'll reply there.
> >
> >
> > Heiko
> >
> > David Summers (2):
> >    ARM: dts: rockchip: move shared tinker-board nodes to a common dtsi
> >    ARM: dts: rockchip: add rk3288-based Tinker board S
> >
> >   .../devicetree/bindings/arm/rockchip.txt      |   4 +
> >   arch/arm/boot/dts/Makefile                    |   1 +
> >   arch/arm/boot/dts/rk3288-tinker-s.dts         |  26 +
> >   arch/arm/boot/dts/rk3288-tinker.dts           | 498 +----------------
> >   arch/arm/boot/dts/rk3288-tinker.dtsi          | 504 ++++++++++++++++++
> >   5 files changed, 537 insertions(+), 496 deletions(-)
> >   create mode 100644 arch/arm/boot/dts/rk3288-tinker-s.dts
> >   create mode 100644 arch/arm/boot/dts/rk3288-tinker.dtsi
> >
> 
> 

      parent reply	other threads:[~2018-10-08  9:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-23 11:38 [PATCH v4 0/2] Reworked rk3288-tinker-s devicetree Heiko Stuebner
2018-09-23 11:38 ` [PATCH v4 1/2] ARM: dts: rockchip: move shared tinker-board nodes to a common dtsi Heiko Stuebner
     [not found] ` <20180923113807.11558-1-heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
2018-09-23 11:38   ` [PATCH v4 2/2] ARM: dts: rockchip: add rk3288-based Tinker board S Heiko Stuebner
     [not found]     ` <20180923113807.11558-3-heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
2018-09-27 18:24       ` Rob Herring
2018-09-23 16:44   ` [PATCH v4 0/2] Reworked rk3288-tinker-s devicetree David Summers
2018-09-26 12:32   ` Heiko Stuebner
2018-10-06 12:54   ` David Summers
     [not found]     ` <5dc8cdc9-20d5-bafa-3693-67ec09577234-8lkWs+DogrrqRUWtDFdff/XRex20P6io@public.gmane.org>
2018-10-08  9:32       ` 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=1701725.aGruVrenYc@phil \
    --to=heiko-4mtyjxux2i+zqb+pc5nmwq@public.gmane.org \
    --cc=beagleboard-8lkWs+DogrrqRUWtDFdff/XRex20P6io@public.gmane.org \
    --cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.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