From: Jani Nikula <jani.nikula@intel.com>
To: David Weinehall <david.weinehall@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH RESEND 2/2] drm/i915: don't register invalid gmbus pins for skl
Date: Mon, 11 May 2015 14:13:24 +0300 [thread overview]
Message-ID: <87y4kv4baj.fsf@intel.com> (raw)
In-Reply-To: <20150511104226.GA2279@boom>
On Mon, 11 May 2015, David Weinehall <david.weinehall@linux.intel.com> wrote:
> On Wed, May 06, 2015 at 03:33:44PM +0300, Jani Nikula wrote:
>> Do no expose invalid gmbus pins as i2c devices to userspace.
>
> "Do not", perchance?
Indeed, and copy-pasted to both...
Jani.
>
>
> Kind regards, David
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-05-11 11:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 12:33 [PATCH RESEND 1/2] drm/i915: don't register invalid gmbus pins for bdw Jani Nikula
2015-05-06 12:33 ` [PATCH RESEND 2/2] drm/i915: don't register invalid gmbus pins for skl Jani Nikula
2015-05-11 10:42 ` David Weinehall
2015-05-11 11:13 ` Jani Nikula [this message]
2015-05-12 11:52 ` Imre Deak
2015-05-12 12:24 ` Jani Nikula
2015-05-12 13:09 ` Daniel Vetter
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=87y4kv4baj.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=david.weinehall@linux.intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox