linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 3/8] Documentation: devicetree: rockchip: Document GeekBox
Date: Tue, 29 Mar 2016 23:21:51 +0200	[thread overview]
Message-ID: <1682289.HWd4yLL18I@diego> (raw)
In-Reply-To: <56FAE95E.6060900@suse.de>

Am Dienstag, 29. M?rz 2016, 22:45:18 schrieb Andreas F?rber:
> Am 29.03.2016 um 22:13 schrieb Heiko St?bner:
> > Am Mittwoch, 16. M?rz 2016, 14:58:41 schrieb Andreas F?rber:
> >> Use "geekbuying,geekbox" compatible string.
> >> 
> >> Acked-by: Rob Herring <robh@kernel.org>
> >> Signed-off-by: Andreas F?rber <afaerber@suse.de>
> > 
> > I've folded this patch into the geekbox dts patch, carrying Rob's Ack for
> > the binding over.
> 
> Either you just made a mistake in my name or
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/tree/Docume
> ntation/devicetree/bindings/submitting-patches.txt needs an update. It
> clearly says:
> 
> "1) The Documentation/ portion of the patch should be a separate patch."
> 
> That's why I always do it this way.

looking at the dt-bindings git log, it seems that is handled in a variety of 
ways :-) . Personally I'm doing completely new bindings separately but the 
125th addition of a board just inside the dts patch.

But I guess we can also move it out again into a separate patch if you prefer 
that :-) .


Heiko

  reply	other threads:[~2016-03-29 21:21 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-16 13:58 [PATCH v4 0/8] arm64: rockchip: Initial GeekBox enablement Andreas Färber
2016-03-16 13:58 ` [PATCH v4 1/8] arm64: dts: rockchip: Clean up /memory nodes Andreas Färber
2016-03-19  8:04   ` Heiko Stuebner
2016-03-31 17:15     ` Heiko Stuebner
2016-03-31 20:45       ` Heiko Stuebner
2016-04-12  5:24         ` Heiko Stuebner
2016-03-16 13:58 ` [PATCH v4 2/8] Documentation: devicetree: Add vendor prefix for GeekBuying.com Andreas Färber
2016-03-28 20:24   ` Heiko Stübner
2016-03-16 13:58 ` [PATCH v4 3/8] Documentation: devicetree: rockchip: Document GeekBox Andreas Färber
2016-03-29 20:13   ` Heiko Stübner
2016-03-29 20:45     ` Andreas Färber
2016-03-29 21:21       ` Heiko Stübner [this message]
2016-03-31 17:02         ` Heiko Stuebner
2016-03-16 13:58 ` [PATCH v4 4/8] arm64: dts: rockchip: Add GeekBox config Andreas Färber
2016-03-29 19:50   ` Heiko Stübner
2016-03-16 13:58 ` [PATCH v4 5/8] arm64: dts: rockchip: Clean up gpio-keys nodes Andreas Färber
2016-03-16 21:55   ` Julien Chauveau
2016-03-28 20:24   ` Heiko Stübner
2016-03-28 20:25     ` Heiko Stübner
2016-03-16 13:58 ` [PATCH v4 6/8] arm64: dts: rockchip: Add power key to GeekBox Andreas Färber
2016-03-16 21:55   ` Julien Chauveau
2016-03-29 20:14   ` Heiko Stübner
2016-03-16 13:58 ` [PATCH v4 7/8] Documentation: devicetree: rockchip: Document Landingship Andreas Färber
2016-03-18 21:30   ` Rob Herring
2016-03-18 21:37     ` Andreas Färber
2016-03-16 13:58 ` [PATCH v4 8/8] arm64: dts: rockchip: Add Landingship config Andreas Färber
2016-03-29 20:18   ` Heiko Stübner
2016-03-29 22:18     ` Andreas Färber

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=1682289.HWd4yLL18I@diego \
    --to=heiko@sntech.de \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).