[PATCH v12 2/4] PM / Domains: add setter for dev.pm_domain

2016-02-09 Thread valdis.kletni...@vt.edu
On Mon, 08 Feb 2016 22:50:39 +0100, "Rafael J. Wysocki" said: > On Mon, Feb 8, 2016 at 10:44 PM, wrote: > > My Dell Latitude laptopi on next-20160201 is throwing a similar error > > at shutdown, except the traceback continues: > > > > mei_me_remove+0xbd/0xc0 > > pci_device_shutdown+0x32/0x50 >

[PATCH v12 2/4] PM / Domains: add setter for dev.pm_domain

2016-02-08 Thread valdis.kletni...@vt.edu
On Fri, 29 Jan 2016 22:35:18 +0100, "Rafael J. Wysocki" said: > > One more test unveils this one > > > > # modprobe -r sdhci-acpi > > [ 1289.909441] [ cut here ] > > [ 1289.918205] WARNING: CPU: 1 PID: 4374 at > > /home/andy/prj/linux-otc/drivers/base/power/common.c:150 >

3.5-rc5: radeon acceleration regression on Transmeta system

2012-07-10 Thread valdis.kletni...@vt.edu
On Mon, 09 Jul 2012 14:30:40 +0300, Meelis Roos said: > It's actually more complicated than that. Old kernel images started > misbehaving from around 2.6.35-rc5 and any kernel older than that was > OK. When I recompiled the older kernels with squeeze gcc (migh have been > lenny gcc before, or

[V5 PATCH 1/4] drivers-gpu-drm-allow-to-load-edid-firmware.patch

2012-03-17 Thread valdis.kletni...@vt.edu
On Thu, 15 Mar 2012 15:56:24 BST, Carsten Emde said: > Broken monitors and/or broken graphic boards may send erroneous or no > EDID data. This also applies to broken KVM devices that are unable to > correctly forward the EDID data of the connected monitor but invent > their own fantasy data. >

[PATCH 1/3] drivers-gpu-drm-allow-to-load-edid-firmware.patch

2012-03-12 Thread valdis.kletni...@vt.edu
On Sat, 10 Mar 2012 21:20:15 +0100, Carsten Emde said: > EDID data source files are provided for documentation purpose and as a > template to create EDID data sets for other screen resolutions. Note > that source compilation is not part of the build process, but needs to > be done manually, e.g.

(Short?) merge window reminder

2011-05-24 Thread valdis.kletni...@vt.edu
On Tue, 24 May 2011 14:30:59 +0200, Jacek Luczak said: > 2011/5/24 Jan Engelhardt : > > On Tuesday 2011-05-24 01:33, Linus Torvalds wrote: > > > >>Another advantage of switching numbering models (ie 3.0 instead of > >>2.8.x) would be that it would also make the "odd numbers are also > >>numbers"

[Ksummit-2010-discuss] [v2] Remaining BKL users, what to do

2010-10-19 Thread valdis.kletni...@vt.edu
On Mon, 18 Oct 2010 17:40:04 PDT, Greg KH said: > I do have access to this hardware, but its on an old single processor > laptop, so any work that it would take to help do this development, > really wouldn't be able to be tested to be valid at all. The i810 is a graphics chipset embedded on the

[PATCH 00/15] change default_llseek action

2010-09-15 Thread valdis.kletni...@vt.edu
On Tue, 14 Sep 2010 22:22:28 +0200, Arnd Bergmann said: > This changes *all* instances of struct file_operations in > the kernel to have a .llseek operation and then changes > the default to no_llseek, which returns -ESPIPE, which > is what we had decided some time ago in a discussion > with

mmotm 2010-07-27 - nouveau lockdep issues.

2010-07-28 Thread valdis.kletni...@vt.edu
On Tue, 27 Jul 2010 14:56:50 PDT, akpm at linux-foundation.org said: > The mm-of-the-moment snapshot 2010-07-27-14-56 has been uploaded to > >http://userweb.kernel.org/~akpm/mmotm/ Hit this while the X server was on its way down during a 'shutdown -r now'. Worked fine in -rc5-mmotm0719.

[PATCH 4/8]drivers:tmp.c Fix warning: variable 'rc' set but not used

2010-06-15 Thread valdis.kletni...@vt.edu
On Mon, 14 Jun 2010 19:12:31 PDT, "Justin P. Mattock" said: > what I tried was this: > > if (!rc) > printk("test"\n") > > and everything looked good, > but as a soon as I changed > > rc = transmit_cmd(chip,_cmd, TPM_INTERNAL_RESULT_SIZE, > "attempting to

[PATCH 4/8]drivers:tmp.c Fix warning: variable 'rc' set but not used

2010-06-14 Thread valdis.kletni...@vt.edu
On Mon, 14 Jun 2010 13:26:44 PDT, "Justin P. Mattock" said: > Im getting this warning when compiling: > CC drivers/char/tpm/tpm.o > drivers/char/tpm/tpm.c: In function 'tpm_gen_interrupt': > drivers/char/tpm/tpm.c:508:10: warning: variable 'rc' set but not used > > The below patch gets rid

linux-next - drm/ttm versus nouveau - WARNING and dead driver.

2010-05-06 Thread valdis.kletni...@vt.edu
On Thu, 06 May 2010 18:56:10 +0200, Jerome Glisse said: > On Thu, May 06, 2010 at 06:16:26PM +0200, Rafa?? Mi??ecki wrote: > > 2010/5/6 : > > > Bisected down to: > > > > > > 82c5da6bf8b55a931b042fb531083863d26c8020 is the first bad commit > > > commit 82c5da6bf8b55a931b042fb531083863d26c8020 > >

linux-next - drm/ttm versus nouveau - WARNING and dead driver.

2010-05-06 Thread valdis.kletni...@vt.edu
Bisected down to: 82c5da6bf8b55a931b042fb531083863d26c8020 is the first bad commit commit 82c5da6bf8b55a931b042fb531083863d26c8020 Author: Jerome Glisse Date: Fri Apr 9 14:39:23 2010 +0200 drm/ttm: ttm_fault callback to allow driver to handle bo placement V6 On fault the driver is

mmotm 2010-04-28 - nouveau driver issues

2010-05-02 Thread valdis.kletni...@vt.edu
On Wed, 28 Apr 2010 16:53:32 PDT, akpm at linux-foundation.org said: > The mm-of-the-moment snapshot 2010-04-28-16-53 has been uploaded to > >http://userweb.kernel.org/~akpm/mmotm/ The nouveau driver had issues during boot, caused plymouth to have indigestion and fall back to 24x80 character