From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: David Airlie <airlied@linux.ie>,
Liviu Dudau <Liviu.Dudau@arm.com>, Jyri Sarha <jsarha@ti.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Sean Paul <seanpaul@chromium.org>,
dri-devel@lists.freedesktop.org, Peter Rosin <peda@axentia.se>,
linux-arm-kernel@lists.infradead.org,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH v2 4/7] drm/i2c: tda998x: convert to bridge driver
Date: Tue, 14 Aug 2018 11:48:13 +0100 [thread overview]
Message-ID: <20180814104812.GV30658@n2100.armlinux.org.uk> (raw)
In-Reply-To: <20180814104242.GO21634@phenom.ffwll.local>
On Tue, Aug 14, 2018 at 12:42:42PM +0200, Daniel Vetter wrote:
> Given your past track record of handling other contributors I think it's
> entirely understandably that people do not choose to collaborate with you
> voluntarily. Fixing that is entirely up to you though.
I do not work piecemeal. I work in blocks, so at some point, I'll
switch to working on X, and then I'll work on X until that's complete
before moving on to Y. It's more efficient use of my time, otherwise
I have to constantly context switch - and that leads to mistakes.
I'm sorry that you don't think that's a good way of working, and you
find that unacceptable, and you blame this on lack of collaboration.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 13.8Mbps down 630kbps up
According to speedtest.net: 13Mbps down 490kbps up
next prev parent reply other threads:[~2018-08-14 10:48 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 16:41 [PATCH v2 0/7] tda998x: allow use with bridge based devices Russell King - ARM Linux
2018-07-30 16:42 ` [PATCH v2 1/7] drm/i2c: tda998x: find the drm_device via the drm_connector Russell King
2018-07-30 16:42 ` [PATCH v2 2/7] drm/i2c: tda998x: split tda998x_encoder_dpms into enable/disable Russell King
2018-07-31 5:46 ` Peter Rosin
2018-07-30 16:42 ` [PATCH v2 3/7] drm/i2c: tda998x: move tda998x_set_config() into tda998x_create() Russell King
2018-07-30 16:42 ` [PATCH v2 4/7] drm/i2c: tda998x: convert to bridge driver Russell King
2018-07-31 7:37 ` Peter Rosin
2018-08-08 19:09 ` Sean Paul
2018-08-08 22:15 ` Russell King - ARM Linux
2018-08-10 16:11 ` Sean Paul
2018-08-10 16:50 ` Russell King - ARM Linux
2018-08-10 17:02 ` Sean Paul
2018-08-10 17:16 ` Russell King - ARM Linux
2018-08-14 10:42 ` Daniel Vetter
2018-08-14 10:48 ` Russell King - ARM Linux [this message]
2018-08-14 11:11 ` Daniel Vetter
2018-08-27 16:15 ` Andrzej Hajda
2018-08-27 17:59 ` Russell King - ARM Linux
2018-08-28 7:31 ` Andrzej Hajda
2018-07-30 16:42 ` [PATCH v2 5/7] drm/i2c: tda998x: allocate tda998x_priv inside tda998x_create() Russell King
2018-07-30 16:42 ` [PATCH v2 6/7] drm/i2c: tda998x: cleanup from previous changes Russell King
2018-07-30 16:42 ` [PATCH v2 7/7] drm/i2c: tda998x: register bridge outside of component helper Russell King
2018-08-27 16:19 ` Andrzej Hajda
2018-07-31 5:44 ` [PATCH v2 0/7] tda998x: allow use with bridge based devices Peter Rosin
2018-07-31 7:41 ` Russell King - ARM Linux
2018-07-31 7:53 ` Peter Rosin
2018-07-31 9:23 ` Russell King - ARM Linux
2018-07-31 9:26 ` [PATCH 1/4] drm/i2c: tda998x: move mode_valid() to bridge Russell King
2018-08-27 16:24 ` Andrzej Hajda
2018-07-31 9:26 ` [PATCH 2/4] drm/i2c: tda998x: get rid of private fill_modes function Russell King
2018-07-31 9:26 ` [PATCH 3/4] drm/i2c: tda998x: correct PLL divider calculation Russell King
2018-07-31 9:26 ` [PATCH 4/4] drm/i2c: tda998x: add support for pixel repeated modes Russell King
2018-07-31 9:42 ` Russell King - ARM Linux
2018-07-31 10:43 ` [PATCH v2 0/7] tda998x: allow use with bridge based devices Peter Rosin
2018-07-31 11:15 ` Russell King - ARM Linux
2018-08-01 9:01 ` Peter Rosin
2018-08-01 9:35 ` Russell King - ARM Linux
2018-08-02 6:06 ` Peter Rosin
2018-11-12 16:50 ` Peter Rosin
2018-11-12 17:00 ` Russell King - ARM Linux
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=20180814104812.GV30658@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=Liviu.Dudau@arm.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jsarha@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=peda@axentia.se \
--cc=seanpaul@chromium.org \
--cc=tomi.valkeinen@ti.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).