From: Jiri Kosina <jikos@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Doug Anderson <dianders@chromium.org>,
Brian Norris <briannorris@chromium.org>,
Caesar Wang <wxt@rock-chips.com>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v2 1/2] devicetree: i2c-hid: Add Wacom digitizer + regulator support
Date: Mon, 12 Dec 2016 09:53:10 +0100 (CET) [thread overview]
Message-ID: <alpine.LNX.2.00.1612120951130.16984@cbobk.fhfr.pm> (raw)
In-Reply-To: <CAL_JsqLpjhHeeKq3PmNToux1Rgkg0M84-dv9HGCOws223ima4w@mail.gmail.com>
Given the timing (merge window being open) and given then NACK given by
Rob, I've now unapplied the patches (the for-4.10/i2c-hid branch is now
obsolete, and has been superseded by for-4.10/i2c-hid-nopower).
However, this is mostly done in order to provide more time for discussion;
I still disagree with the reasoning behind the NACK.
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2016-12-12 8:53 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 1:21 [PATCH v2 1/2] devicetree: i2c-hid: Add Wacom digitizer + regulator support Brian Norris
2016-12-01 1:21 ` [PATCH v2 2/2] HID: i2c-hid: support Wacom digitizer + regulator Brian Norris
2016-12-01 14:41 ` Benjamin Tissoires
2016-12-01 17:30 ` Brian Norris
2016-12-01 14:34 ` [PATCH v2 1/2] devicetree: i2c-hid: Add Wacom digitizer + regulator support Benjamin Tissoires
2016-12-01 17:24 ` Brian Norris
2016-12-05 23:59 ` Rob Herring
2016-12-06 0:16 ` Dmitry Torokhov
2016-12-06 8:48 ` Benjamin Tissoires
2016-12-06 14:56 ` Rob Herring
2016-12-06 16:18 ` Doug Anderson
2016-12-08 15:41 ` Benjamin Tissoires
2016-12-08 16:03 ` Rob Herring
2016-12-08 16:13 ` Dmitry Torokhov
2016-12-08 16:26 ` Rob Herring
2016-12-08 18:12 ` Dmitry Torokhov
2016-12-09 14:36 ` Rob Herring
2016-12-09 14:36 ` Jiri Kosina
2016-12-09 15:01 ` Rob Herring
2016-12-09 16:16 ` Doug Anderson
2016-12-12 8:53 ` Jiri Kosina [this message]
2016-12-12 10:01 ` Benjamin Tissoires
2016-12-12 14:47 ` Rob Herring
2016-12-12 18:34 ` Brian Norris
2016-12-13 22:10 ` Rob Herring
2016-12-08 16:01 ` Rob Herring
2016-12-09 16:05 ` Doug Anderson
2016-12-09 17:44 ` Rob Herring
2016-12-05 23:42 ` Rob Herring
2016-12-05 23:54 ` Brian Norris
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=alpine.LNX.2.00.1612120951130.16984@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=benjamin.tissoires@redhat.com \
--cc=briannorris@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh@kernel.org \
--cc=wxt@rock-chips.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).