On Mon, 27 Jan 2020, "Bharadiya,Pankaj"
wrote:
> On Thu, Jan 23, 2020 at 11:39:37AM +0200, Jani Nikula wrote:
>> On Thu, 23 Jan 2020, "Bharadiya,Pankaj"
>> wrote:
>> > Will rebase remaining patches and submit.
>>
>> Please also add a patch to convert MISSING_CASE(),
>
> Will do.
>
>> and anoth
On Thu, Jan 23, 2020 at 11:39:37AM +0200, Jani Nikula wrote:
> On Thu, 23 Jan 2020, "Bharadiya,Pankaj"
> wrote:
> > Will rebase remaining patches and submit.
>
> Please also add a patch to convert MISSING_CASE(),
Will do.
> and another to remove
> the WARN_ON/WARN_ON_ONCE "overrides" that we h
On Thu, 23 Jan 2020, "Bharadiya,Pankaj"
wrote:
> Will rebase remaining patches and submit.
Please also add a patch to convert MISSING_CASE(), and another to remove
the WARN_ON/WARN_ON_ONCE "overrides" that we have in i915_utils.h.
Thanks,
Jani.
--
Jani Nikula, Intel Open Source Graphics Cente
On Wed, Jan 22, 2020 at 06:22:17PM +0200, Jani Nikula wrote:
> On Wed, 15 Jan 2020, Pankaj Bharadiya
> wrote:
> > Device specific dev_WARN and dev_WARN_ONCE macros available in kernel
> > include device information in the backtrace, so we know what device
> > the warnings originate from.
> >
> >
On Wed, 15 Jan 2020, Pankaj Bharadiya
wrote:
> Device specific dev_WARN and dev_WARN_ONCE macros available in kernel
> include device information in the backtrace, so we know what device
> the warnings originate from.
>
> Similar to this, add new struct drm_device based drm_WARN* macros. These
>
Device specific dev_WARN and dev_WARN_ONCE macros available in kernel
include device information in the backtrace, so we know what device
the warnings originate from.
Similar to this, add new struct drm_device based drm_WARN* macros. These
macros include device information in the backtrace, so we
Device specific dev_WARN and dev_WARN_ONCE macros available in kernel
include device information in the backtrace, so we know what device
the warnings originate from.
Similar to this, add new struct drm_device based drm_WARN* macros. These
macros include device information in the backtrace, so we