From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] i2c: meson: add gxbb compatible string
Date: Sat, 24 Sep 2016 10:41:54 +0200 [thread overview]
Message-ID: <20160924084154.GA1434@katana> (raw)
In-Reply-To: <CAL_JsqJGQ2az=eO0PbfcTrAPxUsym=UaDOOy1Rsw0-AbzMjnXg@mail.gmail.com>
> I did state some reasons previously. Consistent rules for submitters
> of DT bindings and being able to trace history beyond git. Now, I
> guess you aren't changing the rules, but you probably aren't
> requesting people to split DT bindings either? You might not be aware,
> but we also generate a DT only tree with git-filter-branch[1] for
> non-kernel projects to use bindings and dts files. For that, sure they
> will only get the DT binding part of it, but what commit text do they
> get? Finally, DT maintainer acks (which from me is a review really)
> apply to the bindings only. Sometimes I review the drivers, but not
> often. So I would like the git history of my reviews to be accurate in
> terms of what I actually reviewed.
Points taken. Will keep them seperate from now on.
Thanks,
Wolfram
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160924/b82a4946/attachment-0001.sig>
prev parent reply other threads:[~2016-09-24 8:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 9:49 [PATCH 0/2] i2c: meson: add gxbb compatible string Jerome Brunet
2016-09-14 9:49 ` [PATCH 1/2] " Jerome Brunet
2016-09-14 15:19 ` Kevin Hilman
2016-09-14 9:49 ` [PATCH 2/2] dt-bindings: i2c-meson: " Jerome Brunet
2016-09-14 15:19 ` Kevin Hilman
2016-09-15 19:41 ` [PATCH 0/2] i2c: meson: " Wolfram Sang
2016-09-23 15:01 ` Rob Herring
2016-09-23 22:13 ` Wolfram Sang
2016-09-23 23:04 ` Rob Herring
2016-09-23 23:26 ` Wolfram Sang
2016-09-24 1:02 ` Rob Herring
2016-09-24 8:41 ` Wolfram Sang [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=20160924084154.GA1434@katana \
--to=wsa@the-dreams.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).