From: Peter Clifton <pcjc2@cam.ac.uk>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Patch review
Date: Sun, 25 Apr 2010 22:28:22 +0100 [thread overview]
Message-ID: <1272230902.26741.28.camel@pcjc2lap> (raw)
Hi guys,
I've sent three patches to the list for review recently, and posed a
question about possible buggy palette handling. Two of the patches I
sent fix bugs (one "real", one a build issue), and there is a one
clean-up.
I've had no replies on any issue yet. I would appreciate if someone
could take a quick look and ACK / NAK the patches.
I'm only a technical user (Although I do some OSS software development
in my free time), and it is somewhat disheartening when I've taken the
extra steps to produce a patch to fix the issues, for them to be
(seemingly) ignored.
If you want me to go away and file bug-reports, and attach the patches,
I'll do it, but these are simple issues - and if people would pick up
and commit the patches I've sent, it saves me a lot of time fighting
bugzilla.
It was me who "discovered" the TV-out logic on the Cantiga platforms
seem to require a "0" in the state-change detection enable bits, but I
see I got no credit for that detective work in the eventual patch Zhao
Yakui worked up once with access to the HW specs / BIOS code.
PS.. Wouldn't it be nice to get some of that reference BIOS code opened
up?
Regards,
--
Peter Clifton
Electrical Engineering Division,
Engineering Department,
University of Cambridge,
9, JJ Thomson Avenue,
Cambridge
CB3 0FA
Tel: +44 (0)7729 980173 - (No signal in the lab!)
Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me)
next reply other threads:[~2010-04-25 21:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-25 21:28 Peter Clifton [this message]
2010-04-26 2:48 ` Patch review Matt Turner
2010-05-05 18:27 ` Carl Worth
2010-05-05 18:25 ` Carl Worth
-- strict thread matches above, loose matches on Subject: below --
2018-02-28 15:07 Guennadi Liakhovetski
2018-02-28 15:21 ` Laurent Pinchart
2018-02-28 15:49 ` Guennadi Liakhovetski
2018-03-08 16:49 ` Mauro Carvalho Chehab
[not found] <200611162312.kAGNCLgn010867@shell0.pdx.osdl.net>
2006-11-17 18:45 ` patch review James Simmons
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=1272230902.26741.28.camel@pcjc2lap \
--to=pcjc2@cam.ac.uk \
--cc=intel-gfx@lists.freedesktop.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.