From: will.deacon@arm•com (Will Deacon)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v2 2/4] Documentation: Add documentation for APM X-Gene SoC PMU DTS binding
Date: Tue, 31 May 2016 17:25:56 +0100 [thread overview]
Message-ID: <20160531162555.GQ24936@arm.com> (raw)
In-Reply-To: <CACgAJHz8bRb6E1xNFwhKpHDGxPhEsQ3J=H_u3woVLgzK0j==Bg@mail.gmail.com>
On Tue, May 24, 2016 at 02:12:19PM -0700, Tai Tri Nguyen wrote:
> It's been weeks.
> I just want to ping again if you have any more comments on this patch set?
We seem to have reached a stalemate whereby:
- The devicetree maintainers don't agree with your binding
- You don't agree with them
- I won't merge the patch without their ack
so I guess you either need to try harder to convince them about the
index-based binding, or bite the bullet and fix it to make them happy.
Will
next prev parent reply other threads:[~2016-05-31 16:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 1:22 [PATCH v2 0/4] perf: Add APM X-Gene SoC Performance Monitoring Unit driver Tai Nguyen
2016-04-13 1:22 ` [PATCH v2 1/4] MAINTAINERS: Add entry for APM X-Gene SoC PMU driver Tai Nguyen
2016-04-13 1:22 ` [PATCH v2 2/4] Documentation: Add documentation for APM X-Gene SoC PMU DTS binding Tai Nguyen
2016-04-18 17:00 ` Rob Herring
2016-04-18 20:04 ` Tai Tri Nguyen
2016-04-20 11:31 ` Will Deacon
2016-04-29 17:08 ` Tai Tri Nguyen
2016-05-02 20:56 ` Rob Herring
2016-05-02 21:46 ` Tai Tri Nguyen
2016-05-10 23:43 ` Tai Tri Nguyen
2016-05-24 21:12 ` Tai Tri Nguyen
2016-05-31 16:25 ` Will Deacon [this message]
2016-05-31 17:18 ` Tai Tri Nguyen
2016-05-31 16:56 ` Mark Rutland
2016-05-31 17:17 ` Tai Tri Nguyen
2016-06-01 1:25 ` Tai Tri Nguyen
2016-06-06 17:29 ` Mark Rutland
2016-06-06 17:55 ` Tai Tri Nguyen
2016-04-13 1:22 ` [PATCH v2 3/4] perf: xgene: Add APM X-Gene SoC Performance Monitoring Unit driver Tai Nguyen
2016-04-13 1:22 ` [PATCH v2 4/4] arm64: dts: apm: Add APM X-Gene SoC PMU DTS entries Tai Nguyen
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=20160531162555.GQ24936@arm.com \
--to=will.deacon@arm$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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