From: Geir Ove Myhr <gomyhr@gmail.com>
To: Keith Packard <keithp@keithp.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] intel: Listen for hotplug uevents (V2)
Date: Mon, 4 Oct 2010 12:51:19 +0200 [thread overview]
Message-ID: <AANLkTi=K9Hdzf=rFEGKBaynw9i9HQqb1MwqX9Z+iN8Fg@mail.gmail.com> (raw)
In-Reply-To: <1286147296-12531-1-git-send-email-keithp@keithp.com>
On Mon, Oct 4, 2010 at 1:08 AM, Keith Packard <keithp@keithp.com> wrote:
> From: Adam Jackson <ajax@redhat.com>
> ...
> +++ b/src/intel_driver.c
> @@ -107,6 +107,7 @@ typedef enum {
> OPTION_DEBUG_FLUSH_BATCHES,
> OPTION_DEBUG_FLUSH_CACHES,
> OPTION_DEBUG_WAIT,
> + OPTION_HOTPLUG,
> } I830Opts;
>
> static OptionInfoRec I830Options[] = {
> @@ -125,6 +126,7 @@ static OptionInfoRec I830Options[] = {
> {OPTION_DEBUG_FLUSH_BATCHES, "DebugFlushBatches", OPTV_BOOLEAN, {0}, FALSE},
> {OPTION_DEBUG_FLUSH_CACHES, "DebugFlushCaches", OPTV_BOOLEAN, {0}, FALSE},
> {OPTION_DEBUG_WAIT, "DebugWait", OPTV_BOOLEAN, {0}, FALSE},
> + {OPTION_HOTPLUG, "HotPlug", OPTV_BOOLEAN, {0}, TRUE},
> {-1, NULL, OPTV_NONE, {0}, FALSE}
> };
> /* *INDENT-ON* */
The HotPlug option should also be added to the intel man page, right?
Geir Ove
next prev parent reply other threads:[~2010-10-04 10:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-03 22:13 [PATCH] intel: Listen for hotplug uevents Keith Packard
2010-10-03 23:08 ` [PATCH] intel: Listen for hotplug uevents (V2) Keith Packard
2010-10-03 23:15 ` Peter Stuge
2010-10-03 23:34 ` Keith Packard
2010-10-04 9:25 ` [Intel-gfx] " Chris Wilson
2010-10-04 10:51 ` Geir Ove Myhr [this message]
2010-10-04 17:43 ` [PATCH] intel: Listen for hotplug uevents (V3) Keith Packard
2010-10-04 20:57 ` Geir Ove Myhr
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='AANLkTi=K9Hdzf=rFEGKBaynw9i9HQqb1MwqX9Z+iN8Fg@mail.gmail.com' \
--to=gomyhr@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=keithp@keithp.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 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.