At Wed, 26 Mar 2014 20:10:09 +0100,
Daniel Vetter wrote:
It apparently blows up on some machines. This functionally reverts
commit 828c79087cec61eaf4c76bb32c222fbe35ac3930
Author: Ben Widawsky benjamin.widaw...@intel.com
Date: Wed Oct 16 09:21:30 2013 -0700
drm/i915: Disable GGTT
On Thu, Mar 27, 2014 at 7:41 AM, Takashi Iwai ti...@suse.de wrote:
It apparently blows up on some machines. This functionally reverts
commit 828c79087cec61eaf4c76bb32c222fbe35ac3930
Author: Ben Widawsky benjamin.widaw...@intel.com
Date: Wed Oct 16 09:21:30 2013 -0700
drm/i915: Disable
At Thu, 27 Mar 2014 07:55:57 +0100,
Daniel Vetter wrote:
On Thu, Mar 27, 2014 at 7:41 AM, Takashi Iwai ti...@suse.de wrote:
It apparently blows up on some machines. This functionally reverts
commit 828c79087cec61eaf4c76bb32c222fbe35ac3930
Author: Ben Widawsky benjamin.widaw...@intel.com
On Tue, Mar 25, 2014 at 09:58:45PM +0200, Aaro Koskinen wrote:
Enabling EARLY_PRINTK_8250 breaks OCTEON builds because of multiple
prom_putchar() implementations. OCTEON provides its own prom_putchar()
(also used by the watchdog driver), so we should prevent user from
selecting
From: Ville Syrjälä ville.syrj...@linux.intel.com
In commit
commit 6375b768a9850b6154478993e5fb566fa4614a9c
Author: Ville Syrjälä ville.syrj...@linux.intel.com
Date: Mon Mar 3 11:33:36 2014 +0200
drm/i915: Reject 165MHz modes w/ DVI monitors
the driver started to filter out display
On Thu, Mar 27, 2014 at 11:08:45AM +0200, ville.syrj...@linux.intel.com wrote:
So relax the checks a bit, and apply the single-link DVI dotclock limit
only when filtering the mode list, and ignore the limit when setting
a user specified mode.
Mind enlightening me as to how this actually works?
Hello Linus and everyone,
Please pull the change below from my aio-fixes git repository at
git://git.kvack.org/~bcrl/aio-fixes.git which fixes a couple of issues
found in the aio page migration code. This patch is applicable to the
3.12 and later stable trees as well. Thanks to all the folks
On Thu, Mar 27, 2014 at 01:03:31PM +0200, Ville Syrjälä wrote:
On Thu, Mar 27, 2014 at 09:37:36AM +, Chris Wilson wrote:
On Thu, Mar 27, 2014 at 11:08:45AM +0200, ville.syrj...@linux.intel.com
wrote:
So relax the checks a bit, and apply the single-link DVI dotclock limit
only when
Commit-ID: ca3ba2a2f4a49a308e7d78c784d51b2332064f15
Gitweb: http://git.kernel.org/tip/ca3ba2a2f4a49a308e7d78c784d51b2332064f15
Author: Jason Wang jasow...@redhat.com
AuthorDate: Fri, 28 Feb 2014 11:30:29 +0800
Committer: H. Peter Anvin h...@linux.intel.com
CommitDate: Thu, 27 Mar 2014
On Thu, Mar 27, 2014 at 6:46 AM, Benjamin LaHaise b...@kvack.org wrote:
Please pull the change below from my aio-fixes git repository
Ugh. This is way late in the release, and the patch makes me go: This
is completely insane, which doesn't really help.
static void aio_free_ring(struct
I'm confused -- is rtlwifi: rtl8188ee: enable MSI interrupts support
still wanted/needed?
John
On Tue, Mar 25, 2014 at 10:48:52AM +0800, Adam Lee wrote:
Add MSI interrupts support, enable it when msi_support flag is true,
also could fallback to pin-based interrupts mode if MSI mode fails.
On 03/27/2014 01:15 PM, John W. Linville wrote:
I'm confused -- is rtlwifi: rtl8188ee: enable MSI interrupts support
still wanted/needed?
I think so, but Adam needs to resubmit both patches in a V3.
Larry
--
To unsubscribe from this list: send the line unsubscribe stable in
the body of a
On Thu, Mar 27, 2014 at 11:16 AM, Linus Torvalds
torva...@linux-foundation.org wrote:
It would all be cleaner if all the setup was done with the
ctx-ring_lock held (you can even *initialize* it to the locked state,
since this is the function that allocates it!) and then it would just
be
On Thu, Mar 27, 2014 at 12:43:13PM -0700, Linus Torvalds wrote:
On Thu, Mar 27, 2014 at 11:16 AM, Linus Torvalds
torva...@linux-foundation.org wrote:
It would all be cleaner if all the setup was done with the
ctx-ring_lock held (you can even *initialize* it to the locked state,
since
On Thu, Mar 27, 2014 at 1:08 PM, Benjamin LaHaise b...@kvack.org wrote:
The patch below is lightly tested -- my migration test case is able to
successfully move the aio ring around multiple times. It still needs to
be run through some more thorough tests (like Trinity). See below for
the
On Thu, Mar 27, 2014 at 01:22:11PM -0700, Linus Torvalds wrote:
On Thu, Mar 27, 2014 at 1:08 PM, Benjamin LaHaise b...@kvack.org wrote:
The patch below is lightly tested -- my migration test case is able to
successfully move the aio ring around multiple times. It still needs to
be run
On Thu, Mar 27, 2014 at 1:57 PM, Benjamin LaHaise b...@kvack.org wrote:
*nod* -- I added that to the below variant.
You still have goto err for cases that have the ctx locked. Which
means that the thing gets free'd while still locked, which causes
problems for lockdep etc, so don't do it.
Do
We could have possibly added an extent_op to the locked_ref while we dropped
locked_ref-lock, so check for this case as well and loop around. Otherwise we
could lose flag updates which would lead to extent tree corruption. Thanks,
cc: stable@vger.kernel.org
Signed-off-by: Josef Bacik
timestamps in v4l2 buffers returned to userspace are updated in
uvc_video_clock_update() which uses timestamps fetched from
uvc_video_clock_decode() by calling unconditionally ktime_get_ts().
Hence setting the module clock param to realtime have no effect
before this patch.
This has been tested
19 matches
Mail list logo
