Hi Stephen,
On 3/1/24 15:30, Shuah Khan wrote:
Hi Stephen,
On 3/1/24 13:46, Stephen Rothwell wrote:
Hi Shuah,
On Fri, 1 Mar 2024 09:05:57 -0700 Shuah Khan wrote:
On 3/1/24 03:43, Stephen Rothwell wrote:
Hi all,
On Fri, 1 Mar 2024 15:15:02 +0800 David Gow wrote:
On Thu, 29 Feb 2024
Hi Stephen,
On 2/28/24 21:26, Stephen Rothwell wrote:
Hi all,
After merging the kunit-next tree, today's linux-next build (x86_64
allmodconfig) failed like this:
In file included from drivers/gpu/drm/tests/drm_buddy_test.c:7:
drivers/gpu/drm/tests/drm_buddy_test.c: In function
Hi Stephen,
On 3/1/24 13:46, Stephen Rothwell wrote:
Hi Shuah,
On Fri, 1 Mar 2024 09:05:57 -0700 Shuah Khan wrote:
On 3/1/24 03:43, Stephen Rothwell wrote:
Hi all,
On Fri, 1 Mar 2024 15:15:02 +0800 David Gow wrote:
On Thu, 29 Feb 2024 at 23:07, Shuah Khan wrote:
I can carry the fix
On 3/1/24 03:43, Stephen Rothwell wrote:
Hi all,
On Fri, 1 Mar 2024 15:15:02 +0800 David Gow wrote:
On Thu, 29 Feb 2024 at 23:07, Shuah Khan wrote:
I can carry the fix through kselftest kunit if it works
for all.
I'm happy for this to go in with the KUnit changes if that's the best
way
On 12/07/2016 07:09 AM, Chris Wilson wrote:
> On Wed, Dec 07, 2016 at 01:58:19PM +, Chris Wilson wrote:
>> Although being a GPU driver most functionality of i915.ko depends upon
>> real hardware, many of its internal interfaces can be "mocked" and so
>> tested independently of any hardware.
Hi Chris,
On 12/08/2016 09:01 AM, Chris Wilson wrote:
> On Thu, Dec 08, 2016 at 08:50:17AM -0700, Shuah Khan wrote:
>> On 12/07/2016 07:09 AM, Chris Wilson wrote:
>>> On Wed, Dec 07, 2016 at 01:58:19PM +, Chris Wilson wrote:
>>>> Although being a GPU driver
assertion failure, should be disabled but not
>> ...
>>
>> I can confirm this was not seen in v4.2 here on Ubuntu/precise AMD64.
>>
>> Regards,
>> - Sedat -
>>
>> [0] http://marc.info/?t=14417666342=1=2
>> [1] http://marc.info/?l=linux-kernel=1
? Should I be concerned about this?
thanks,
-- Shuah
--
Shuah Khan
Sr. Linux Kernel Developer
Open Source Innovation Group
Samsung Research America (Silicon Valley)
shua...@osg.samsung.com | (970) 217-8978
___
Intel-gfx mailing list
Intel-gfx
if this helpful, but I thought I would ask just in case, it
helps you think of something you didn't before. Please let me know if
you need help gathering data from my system.
-- Shuah
Shuah Khan, Linux Kernel Developer - Open Source Group Samsung Research
America (Silicon Valley) shuah
On 06/26/2013 04:24 PM, Shuah Khan wrote:
On 06/26/2013 04:12 PM, Winkler, Tomas wrote:
42f132f mei: me: clear interrupts on the resume path
2753ff5 mei: nfc: fix nfc device freeing
5e85b36 mei: init: Flush scheduled work before resetting the device
Are you sure you have these 3
On 06/25/2013 02:06 PM, Jesse Barnes wrote:
On Tue, 25 Jun 2013 19:59:28 +
Shuah Khan shuah...@samsung.com wrote:
On 06/25/2013 01:52 PM, Jesse Barnes wrote:
On Tue, 25 Jun 2013 21:37:37 +0200
Daniel Vetter daniel.vet...@ffwll.ch wrote:
Adding more lists to cc + Jesse since he's
haven't
noticed any other problems.
-- Shuah
Shuah Khan, Linux Kernel Developer - Open Source Group Samsung Research
America (Silicon Valley) shuah...@samsung.com | (970) 672-0658
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http
On 06/25/2013 02:57 PM, Tomas Winkler wrote:
On Tue, Jun 25, 2013 at 11:51 PM, Shuah Khan shuah...@samsung.com wrote:
With this patch warn_on went away. Resume worked. I started seeing:
[ 78.733062] mei_me :00:16.0: unexpected reset: dev_state =
RESETTING
[ 78.733079] mei_me
at least on 3.10-rc7. I
tried several times yesterday to capture the log and couldn't reproduce.
-- Shuah
Shuah Khan, Linux Kernel Developer - Open Source Group Samsung Research
America (Silicon Valley) shuah...@samsung.com | (970) 672-0658
___
Intel-gfx
14 matches
Mail list logo
