All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Anholt <eric@anholt.net>
To: Stephen Warren <swarren@wwwdotorg.org>,
	Stefan Wahren <info@lategoodbye.de>
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-rpi-kernel@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: bcm2835 (Raspberry Pi) KMS driver
Date: Mon, 12 Oct 2015 13:53:28 -0700	[thread overview]
Message-ID: <8737xf6c6v.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <561C1A67.1060803@wwwdotorg.org>

[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]

Stephen Warren <swarren@wwwdotorg.org> writes:

> On 10/11/2015 06:39 AM, Stefan Wahren wrote:
>> Am 09.10.2015 um 23:27 schrieb Eric Anholt:
>>> This is a respin of the Raspberry Pi KMS series.  Now that we've got a
>>> real clock driver, I can actually set new video modes.  Also in this
>>> version, most of the custom DT stuff from before is gone, thanks to
>>> finding exynos's platform_driver component matching code (I have sent
>>> separate patches to drivers/base to make helpers for doing it).
>>>
>>> https://github.com/anholt/linux/tree/vc4-kms-squash-2
>>
>> I want to point out that git format-patch could prepare a nice cover
>> letter and usually the changelog should go there.
>
> Well, I guess you could put it there, but that wouldn't remove the need 
> to put the changelog in the individual patches too, so that reviewers 
> don't have to switch back and forth between different messages just to 
> find out what changed in each patch.
>
> +1 on sending the cover letter using git format-patch/send-email 
> thoughl; the threading here is a little odd.

I was using git send-email --compose.  I guess I'll play with
format-patch --cover-letter, but it seems odd that threading would be
any different between the two.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Eric Anholt <eric@anholt.net>
To: Stephen Warren <swarren@wwwdotorg.org>,
	Stefan Wahren <info@lategoodbye.de>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-rpi-kernel@lists.infradead.org
Subject: Re: bcm2835 (Raspberry Pi) KMS driver
Date: Mon, 12 Oct 2015 13:53:28 -0700	[thread overview]
Message-ID: <8737xf6c6v.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <561C1A67.1060803@wwwdotorg.org>


[-- Attachment #1.1: Type: text/plain, Size: 1264 bytes --]

Stephen Warren <swarren@wwwdotorg.org> writes:

> On 10/11/2015 06:39 AM, Stefan Wahren wrote:
>> Am 09.10.2015 um 23:27 schrieb Eric Anholt:
>>> This is a respin of the Raspberry Pi KMS series.  Now that we've got a
>>> real clock driver, I can actually set new video modes.  Also in this
>>> version, most of the custom DT stuff from before is gone, thanks to
>>> finding exynos's platform_driver component matching code (I have sent
>>> separate patches to drivers/base to make helpers for doing it).
>>>
>>> https://github.com/anholt/linux/tree/vc4-kms-squash-2
>>
>> I want to point out that git format-patch could prepare a nice cover
>> letter and usually the changelog should go there.
>
> Well, I guess you could put it there, but that wouldn't remove the need 
> to put the changelog in the individual patches too, so that reviewers 
> don't have to switch back and forth between different messages just to 
> find out what changed in each patch.
>
> +1 on sending the cover letter using git format-patch/send-email 
> thoughl; the threading here is a little odd.

I was using git send-email --compose.  I guess I'll play with
format-patch --cover-letter, but it seems odd that threading would be
any different between the two.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: eric@anholt.net (Eric Anholt)
To: linux-arm-kernel@lists.infradead.org
Subject: bcm2835 (Raspberry Pi) KMS driver
Date: Mon, 12 Oct 2015 13:53:28 -0700	[thread overview]
Message-ID: <8737xf6c6v.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <561C1A67.1060803@wwwdotorg.org>

Stephen Warren <swarren@wwwdotorg.org> writes:

> On 10/11/2015 06:39 AM, Stefan Wahren wrote:
>> Am 09.10.2015 um 23:27 schrieb Eric Anholt:
>>> This is a respin of the Raspberry Pi KMS series.  Now that we've got a
>>> real clock driver, I can actually set new video modes.  Also in this
>>> version, most of the custom DT stuff from before is gone, thanks to
>>> finding exynos's platform_driver component matching code (I have sent
>>> separate patches to drivers/base to make helpers for doing it).
>>>
>>> https://github.com/anholt/linux/tree/vc4-kms-squash-2
>>
>> I want to point out that git format-patch could prepare a nice cover
>> letter and usually the changelog should go there.
>
> Well, I guess you could put it there, but that wouldn't remove the need 
> to put the changelog in the individual patches too, so that reviewers 
> don't have to switch back and forth between different messages just to 
> find out what changed in each patch.
>
> +1 on sending the cover letter using git format-patch/send-email 
> thoughl; the threading here is a little odd.

I was using git send-email --compose.  I guess I'll play with
format-patch --cover-letter, but it seems odd that threading would be
any different between the two.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20151012/1903f176/attachment.sig>

  reply	other threads:[~2015-10-12 20:53 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-09 21:27 bcm2835 (Raspberry Pi) KMS driver Eric Anholt
2015-10-09 21:27 ` Eric Anholt
2015-10-09 21:27 ` Eric Anholt
2015-10-09 21:27 ` [PATCH v3 1/7] drm/vc4: Add devicetree bindings for VC4 Eric Anholt
2015-10-09 21:27   ` Eric Anholt
2015-10-09 21:27   ` Eric Anholt
2015-10-09 23:31   ` Sebastian Reichel
2015-10-09 23:31     ` Sebastian Reichel
2015-10-09 23:31     ` Sebastian Reichel
2015-10-13 17:59     ` Eric Anholt
2015-10-13 17:59       ` Eric Anholt
2015-10-13 13:26   ` Rob Herring
2015-10-13 13:26     ` Rob Herring
2015-10-13 13:26     ` Rob Herring
2015-10-13 18:17     ` Eric Anholt
2015-10-13 18:17       ` Eric Anholt
2015-10-13 18:17       ` Eric Anholt
2015-10-13 21:56       ` Rob Herring
2015-10-13 21:56         ` Rob Herring
2015-10-13 21:56         ` Rob Herring
2015-10-21  8:57         ` Eric Anholt
2015-10-21  8:57           ` Eric Anholt
2015-10-21  8:57           ` Eric Anholt
2015-10-21 22:08           ` Rob Herring
2015-10-21 22:08             ` Rob Herring
2015-10-21 22:08             ` Rob Herring
2015-10-09 21:27 ` [PATCH v3 2/7] MAINTAINERS: Add myself for the new VC4 (RPi GPU) graphics driver Eric Anholt
2015-10-09 21:27   ` Eric Anholt
2015-10-09 21:27   ` Eric Anholt
2015-10-09 22:12   ` Emil Velikov
2015-10-09 22:12     ` Emil Velikov
2015-10-09 22:12     ` Emil Velikov
2015-10-09 23:13     ` Eric Anholt
2015-10-09 23:13       ` Eric Anholt
2015-10-09 23:13       ` Eric Anholt
2015-10-09 21:27 ` [PATCH v3 3/7] drm/vc4: Add KMS support for Raspberry Pi Eric Anholt
2015-10-09 21:27   ` Eric Anholt
2015-10-09 21:27   ` Eric Anholt
2015-10-11 14:02   ` Stefan Wahren
2015-10-11 14:02     ` Stefan Wahren
2015-10-11 14:02     ` Stefan Wahren
2015-10-13 18:19     ` Eric Anholt
2015-10-13 18:19       ` Eric Anholt
2015-10-13 18:19       ` Eric Anholt
2015-10-13 18:50       ` Stefan Wahren
2015-10-13 18:50         ` Stefan Wahren
2015-10-13 18:50         ` Stefan Wahren
2015-10-13 19:01         ` Stefan Wahren
2015-10-13 19:01           ` Stefan Wahren
2015-10-09 21:27 ` [PATCH v3 4/7] drm/vc4: Use the fbdev_cma helpers Eric Anholt
2015-10-09 21:27   ` Eric Anholt
2015-10-09 21:27   ` Eric Anholt
2015-10-09 21:27 ` [PATCH v3 5/7] drm/vc4: Allow vblank to be disabled Eric Anholt
2015-10-09 21:27   ` Eric Anholt
2015-10-09 21:27   ` Eric Anholt
2015-10-09 21:27 ` [PATCH v3 6/7] ARM: bcm2835: Add the DDC I2C controller to the device tree Eric Anholt
2015-10-09 21:27   ` Eric Anholt
2015-10-09 21:27   ` Eric Anholt
2015-10-09 21:27 ` [PATCH v3 7/7] ARM: bcm2835: Add VC4 " Eric Anholt
2015-10-09 21:27   ` Eric Anholt
2015-10-09 21:27   ` Eric Anholt
2015-10-11 14:23   ` Stefan Wahren
2015-10-11 14:23     ` Stefan Wahren
2015-10-12 20:57     ` Eric Anholt
2015-10-12 20:57       ` Eric Anholt
2015-10-12 20:57       ` Eric Anholt
2015-10-11 12:39 ` bcm2835 (Raspberry Pi) KMS driver Stefan Wahren
2015-10-11 12:39   ` Stefan Wahren
2015-10-11 12:39   ` Stefan Wahren
2015-10-12 20:39   ` Stephen Warren
2015-10-12 20:39     ` Stephen Warren
2015-10-12 20:39     ` Stephen Warren
2015-10-12 20:53     ` Eric Anholt [this message]
2015-10-12 20:53       ` Eric Anholt
2015-10-12 20:53       ` Eric Anholt

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=8737xf6c6v.fsf@eliezer.anholt.net \
    --to=eric@anholt.net \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=info@lategoodbye.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=swarren@wwwdotorg.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.