All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Airlie <airlied@linux.ie>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	DRI <dri-devel@lists.freedesktop.org>,
	Nick Dyer <nick.dyer@itdev.co.uk>,
	Olof Johansson <olof@lixom.net>,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH v2] drm/i915: cope with large i2c transfers
Date: Thu, 23 Apr 2015 23:53:21 +0300	[thread overview]
Message-ID: <87h9s6woqm.fsf@intel.com> (raw)
In-Reply-To: <20150423161607.GN5082@phenom.ffwll.local>

On Thu, 23 Apr 2015, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Tue, Apr 21, 2015 at 10:12:19AM -0700, Linus Torvalds wrote:
>> On Tue, Apr 21, 2015 at 9:49 AM, Dmitry Torokhov
>> <dmitry.torokhov@gmail.com> wrote:
>> > The hardware, according to the specs, is limited to 256 byte transfers,
>> > and current driver has no protections in case users attempt to do larger
>> > transfers. The code will just stomp over status register and mayhem
>> > ensues.
>> 
>> Thanks, looks good.
>> 
>> David/Daniel - should I take this directly, or can I expect to just
>> get it from the drm tree?
>
> I asked Jani to pick this up. I'm horribly jetlagged and just repacking
> for my vacation so probably shouldn't touch git branches right now ;-)

Pushed to drm-intel-next-fixes, thanks for the patch and review. I'll
gather a few more fixes and send the pull req to Dave later.

BR,
Jani.


> -Daniel
> -- 
> Daniel Vetter
> Software Engineer, Intel Corporation
> http://blog.ffwll.ch
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Airlie <airlied@linux.ie>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Nick Dyer <nick.dyer@itdev.co.uk>,
	DRI <dri-devel@lists.freedesktop.org>,
	Olof Johansson <olof@lixom.net>,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [Intel-gfx] [PATCH v2] drm/i915: cope with large i2c transfers
Date: Thu, 23 Apr 2015 23:53:21 +0300	[thread overview]
Message-ID: <87h9s6woqm.fsf@intel.com> (raw)
In-Reply-To: <20150423161607.GN5082@phenom.ffwll.local>

On Thu, 23 Apr 2015, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Tue, Apr 21, 2015 at 10:12:19AM -0700, Linus Torvalds wrote:
>> On Tue, Apr 21, 2015 at 9:49 AM, Dmitry Torokhov
>> <dmitry.torokhov@gmail.com> wrote:
>> > The hardware, according to the specs, is limited to 256 byte transfers,
>> > and current driver has no protections in case users attempt to do larger
>> > transfers. The code will just stomp over status register and mayhem
>> > ensues.
>> 
>> Thanks, looks good.
>> 
>> David/Daniel - should I take this directly, or can I expect to just
>> get it from the drm tree?
>
> I asked Jani to pick this up. I'm horribly jetlagged and just repacking
> for my vacation so probably shouldn't touch git branches right now ;-)

Pushed to drm-intel-next-fixes, thanks for the patch and review. I'll
gather a few more fixes and send the pull req to Dave later.

BR,
Jani.


> -Daniel
> -- 
> Daniel Vetter
> Software Engineer, Intel Corporation
> http://blog.ffwll.ch
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Jani Nikula, Intel Open Source Technology Center

  reply	other threads:[~2015-04-23 20:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-21 16:49 [PATCH v2] drm/i915: cope with large i2c transfers Dmitry Torokhov
2015-04-21 17:12 ` Linus Torvalds
2015-04-21 17:12   ` Linus Torvalds
2015-04-23 16:16   ` Daniel Vetter
2015-04-23 16:16     ` [Intel-gfx] " Daniel Vetter
2015-04-23 20:53     ` Jani Nikula [this message]
2015-04-23 20:53       ` Jani Nikula

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=87h9s6woqm.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=airlied@linux.ie \
    --cc=daniel.vetter@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=dmitry.torokhov@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nick.dyer@itdev.co.uk \
    --cc=olof@lixom.net \
    --cc=torvalds@linux-foundation.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.