From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: James Simmons <jsimmons@infradead.org>
Cc: OpenChrome Development <Openchrome-devel@lists.freedesktop.org>,
DRI development list <dri-devel@lists.freedesktop.org>
Subject: Re: [RPC 0/21] DRM: Add VIA DRM driver
Date: Mon, 10 Jun 2013 09:31:38 -0400 [thread overview]
Message-ID: <20130610133138.GD4504@phenom.dumpdata.com> (raw)
In-Reply-To: <alpine.LFD.2.03.1306081735520.18671@infradead.org>
On Sat, Jun 08, 2013 at 05:42:20PM +0100, James Simmons wrote:
>
> Hello
>
> Here is the first run at inspection of the VIA openchrome dri
> driver. Now that the Xorg driver has been out over a year with KMS support
> most people should be able to use this feature. The driver is totaly
> complete but we wanted to merge it so people with newer hardware that has
> HDMI/DVI-D support can be able to run X windows. Your xorg driver does not
> implement HDMI/DVI in UMS mode and we don't have the resources to do this
> work. Basic TTM/GEM is supported but currently you can't run any
> acceleration with the command queue. Over the next 6 months this should be
> implemented. Thank you.
Hey James,
I am not entirely sure what happend but it looks like you are using
Alpine mailer to send out the patches. The sad end result is that
all of the patches have the "DRM: Add VIA DRM driver" title instead
of the more appropiate title within the email.
Could you repost them with 'git send-email' please?
This link http://kernelnewbies.org/OPWfirstpatch
at the "Submit a patch" section has an excellent tutorial on how
to use different mailers. The "Setup your tools" has a nice
tutorial on .gitconfig setup. If you would like to use
me as test subject and send emails to me before the mailing list
please do.
I usually have this in my .gitconfig file:
[konrad@build-external ~]$ more .gitconfig
[user]
name = Konrad Rzeszutek Wilk
email = konrad.wilk@oracle.com
signingkey = F1DB09BF
[color]
branch = true
diff = true
[sendemail]
smtpserver = smtp.gmail.com
smtpserverport = 587
smtpencryption = tls
smtpuser = ketuzsezr@gmail.com
and for sending emails to myself I do:
konrad@phenom:~/linux$ git format-patch --subject-prefix="v4" HEAD^^..
0001-xen-ring-Add-a-new-macro-to-detect-whether-there-is-.patch
0002-xen-blkback-Check-for-insane-amounts-of-request-on-t.patch
then:
konrad@phenom:~/linux: git send-email --suppress-cc=all --to konrad@kernel.org --compose --annotate --subject "[PATCH v4] Safety harness for the block driver." *.patch
edit in vim the changes, look over all of the patches, and then send.
Lastly, is there a git tree with these patches so that one may
just in one swoop test them out?
Thanks!
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
next prev parent reply other threads:[~2013-06-10 13:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-08 16:42 [RPC 0/21] DRM: Add VIA DRM driver James Simmons
2013-06-10 13:31 ` Konrad Rzeszutek Wilk [this message]
2013-06-10 14:58 ` Daniel Vetter
2013-06-10 23:10 ` Dave Airlie
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=20130610133138.GD4504@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Openchrome-devel@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jsimmons@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.