From: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
To: Jani Nikula <jani.nikula@linux.intel.com>, igt-dev@lists.freedesktop.org
Cc: Petri Latvala <petri.latvala@intel.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [igt-dev] [PATCH i-g-t] lib/igt_edid_template: Fix parenthesis for vertical pulse coding
Date: Fri, 18 Jan 2019 16:17:57 +0100 [thread overview]
Message-ID: <4e1350350bc1a2246b223e38cf865a62422f3e04.camel@bootlin.com> (raw)
In-Reply-To: <87bm4i6zh1.fsf@intel.com>
Hi,
On Tue, 2019-01-15 at 11:29 +0200, Jani Nikula wrote:
> On Mon, 14 Jan 2019, Paul Kocialkowski <paul.kocialkowski@bootlin.com> wrote:
> > Looks like this patch was reviewed and CI-tested, so it should be ready
> > for inclusion. Would someone like to pick it up?
>
> For future reference, you could ask for commit rights, and push your own
> patches after review and CI. See CONTRIBUTING.md.
Yes, given that we have been working with IGT quite a lot recently,
that would make sense. I'll be discussing this with Maxime soon then!
Cheers,
Paul
--
Paul Kocialkowski, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
prev parent reply other threads:[~2019-01-18 15:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 16:54 [igt-dev] [PATCH i-g-t] lib/igt_edid_template: Fix parenthesis for vertical pulse coding Paul Kocialkowski
2019-01-03 17:17 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-01-03 18:11 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-01-07 14:39 ` [igt-dev] [PATCH i-g-t] " Ville Syrjälä
2019-01-14 14:20 ` Paul Kocialkowski
2019-01-14 19:25 ` Antonio Argenziano
2019-01-15 9:29 ` Jani Nikula
2019-01-18 15:17 ` Paul Kocialkowski [this message]
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=4e1350350bc1a2246b223e38cf865a62422f3e04.camel@bootlin.com \
--to=paul.kocialkowski@bootlin.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=petri.latvala@intel.com \
--cc=thomas.petazzoni@bootlin.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