From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC 1/3] DRM: Armada: Add Armada DRM driver
Date: Mon, 01 Jul 2013 10:52:03 +0200 [thread overview]
Message-ID: <51D14333.40307@gmail.com> (raw)
In-Reply-To: <CAPM=9tydcpP2-A6fnnHB873Nekj4HnxjraZ3TtRG3UF-Bqa6OQ@mail.gmail.com>
On 07/01/13 02:01, Dave Airlie wrote:
> how about instead of writing:
> "However, at least I've taken the time to_think_ about what I'm doing
> and realise that there_is_ scope here for the DRM core to improve,
> rather than burying this stuff deep inside my driver like everyone else
> has. That's no reason to penalise patches from the "good guys" who think"
>
> you go with
> "I noticed this piece of functionality could be refactored, here is a
> patch adding them to
> the core, does anyone think its a good idea?"
Dave,
at least on this point I do share Russell's impression. I've sent
bunch of patches improving TDA998x and DRM+DT:
- TDA998x irq handling - ignored
- TDA998x sync fix - ignored
- Fix drm I2C slave encoder probing
I am aware that this is not an easy job nor one you get much
appreciation for. But, back when TDA998x driver was published,
all my comments were basically answered with "Oh, I know. Maybe
someday somebody will fix it".
I am not being paid for any of this, but have a strong intrinsic
motivation here. But I am loosing interest in sending fixes for
DRM stuff because my (personal) impression is the same Russell
has: Depending on who sends patches, they get merged independent
of how broken they are - others are discussed to death.
Sebastian
WARNING: multiple messages have this Message-ID (diff)
From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Dave Airlie <airlied@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
dri-devel@lists.freedesktop.org, Daniel Vetter <daniel@ffwll.ch>,
Jason Cooper <jason@lakedaemon.net>
Subject: Re: [PATCH RFC 1/3] DRM: Armada: Add Armada DRM driver
Date: Mon, 01 Jul 2013 10:52:03 +0200 [thread overview]
Message-ID: <51D14333.40307@gmail.com> (raw)
In-Reply-To: <CAPM=9tydcpP2-A6fnnHB873Nekj4HnxjraZ3TtRG3UF-Bqa6OQ@mail.gmail.com>
On 07/01/13 02:01, Dave Airlie wrote:
> how about instead of writing:
> "However, at least I've taken the time to_think_ about what I'm doing
> and realise that there_is_ scope here for the DRM core to improve,
> rather than burying this stuff deep inside my driver like everyone else
> has. That's no reason to penalise patches from the "good guys" who think"
>
> you go with
> "I noticed this piece of functionality could be refactored, here is a
> patch adding them to
> the core, does anyone think its a good idea?"
Dave,
at least on this point I do share Russell's impression. I've sent
bunch of patches improving TDA998x and DRM+DT:
- TDA998x irq handling - ignored
- TDA998x sync fix - ignored
- Fix drm I2C slave encoder probing
I am aware that this is not an easy job nor one you get much
appreciation for. But, back when TDA998x driver was published,
all my comments were basically answered with "Oh, I know. Maybe
someday somebody will fix it".
I am not being paid for any of this, but have a strong intrinsic
motivation here. But I am loosing interest in sending fixes for
DRM stuff because my (personal) impression is the same Russell
has: Depending on who sends patches, they get merged independent
of how broken they are - others are discussed to death.
Sebastian
next prev parent reply other threads:[~2013-07-01 8:52 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-29 22:52 [PATCH RFC v4 0/3] Armada DRM driver Russell King - ARM Linux
2013-06-29 22:52 ` Russell King - ARM Linux
2013-06-29 22:53 ` [PATCH RFC 1/3] DRM: Armada: Add " Russell King
2013-06-29 22:56 ` Russell King
2013-06-30 11:59 ` Daniel Vetter
2013-06-30 11:59 ` Daniel Vetter
2013-06-30 12:52 ` Russell King - ARM Linux
2013-06-30 12:52 ` Russell King - ARM Linux
2013-06-30 17:29 ` Daniel Vetter
2013-06-30 17:29 ` Daniel Vetter
2013-07-02 18:01 ` Ville Syrjälä
2013-07-02 18:01 ` Ville Syrjälä
2013-07-02 18:23 ` Russell King - ARM Linux
2013-07-02 18:23 ` Russell King - ARM Linux
2013-07-02 18:52 ` Ville Syrjälä
2013-07-02 18:52 ` Ville Syrjälä
2013-07-01 0:01 ` Dave Airlie
2013-07-01 0:01 ` Dave Airlie
2013-07-01 0:17 ` Russell King - ARM Linux
2013-07-01 0:17 ` Russell King - ARM Linux
2013-07-01 0:40 ` Dave Airlie
2013-07-01 0:40 ` Dave Airlie
2013-07-01 8:52 ` Sebastian Hesselbarth [this message]
2013-07-01 8:52 ` Sebastian Hesselbarth
2013-07-01 9:42 ` Daniel Vetter
2013-07-01 9:42 ` Daniel Vetter
2013-07-01 10:50 ` Sebastian Hesselbarth
2013-07-01 10:50 ` Sebastian Hesselbarth
2013-07-01 21:26 ` Dave Airlie
2013-07-01 21:26 ` Dave Airlie
2013-07-01 23:33 ` Rob Clark
2013-07-01 23:33 ` Rob Clark
2013-07-01 21:55 ` Rob Clark
2013-07-01 21:55 ` Rob Clark
2013-07-01 22:07 ` Sebastian Hesselbarth
2013-07-01 22:07 ` Sebastian Hesselbarth
2013-06-30 12:37 ` Daniel Vetter
2013-06-30 12:37 ` Daniel Vetter
2013-06-30 13:04 ` Russell King - ARM Linux
2013-06-30 13:04 ` Russell King - ARM Linux
2013-06-30 13:41 ` Russell King - ARM Linux
2013-06-30 13:41 ` Russell King - ARM Linux
2013-06-30 13:53 ` Russell King - ARM Linux
2013-06-30 13:53 ` Russell King - ARM Linux
2013-06-30 16:58 ` Daniel Vetter
2013-06-30 16:58 ` Daniel Vetter
2013-06-29 22:54 ` [PATCH RFC 2/3] DRM: Armada: Add support for ARGB 32x64 or 64x32 hardware cursors Russell King
2013-06-29 22:54 ` Russell King
2013-06-29 22:55 ` [PATCH RFC 3/3] DRM: Armada: support for dma_buf import into gem Russell King
2013-06-29 22:55 ` Russell King
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=51D14333.40307@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.