From: "Bharadiya,Pankaj" <pankaj.laxminarayan.bharadiya@intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
sam@ravnborg.org, sudeep.dutt@intel.com
Subject: Re: [[Intel-gfx] [PATCH v2 00/10] drm: Introduce struct drm_device based WARN* and use them in i915
Date: Mon, 27 Jan 2020 13:44:24 +0530 [thread overview]
Message-ID: <20200127081423.GB8711@plaxmina-desktop.iind.intel.com> (raw)
In-Reply-To: <87blquik9y.fsf@intel.com>
On Thu, Jan 23, 2020 at 11:39:37AM +0200, Jani Nikula wrote:
> On Thu, 23 Jan 2020, "Bharadiya,Pankaj" <pankaj.laxminarayan.bharadiya@intel.com> 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 have in i915_utils.h.
Still i915 driver wil have many calls to WARN_ON* after this patch
series gets merged.
Shall I remove WARN_ON/WARN_ON_ONCE "overrides" so that existing
callers will fallback to original WARN_ON* implementation until
complete conversion is done? Just want to double confirm on this
before I submit a patch.
Thanks,
Pankaj
>
> Thanks,
> Jani.
>
> --
> Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: "Bharadiya,Pankaj" <pankaj.laxminarayan.bharadiya@intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
sam@ravnborg.org
Subject: Re: [Intel-gfx] [ [PATCH v2 00/10] drm: Introduce struct drm_device based WARN* and use them in i915
Date: Mon, 27 Jan 2020 13:44:24 +0530 [thread overview]
Message-ID: <20200127081423.GB8711@plaxmina-desktop.iind.intel.com> (raw)
In-Reply-To: <87blquik9y.fsf@intel.com>
On Thu, Jan 23, 2020 at 11:39:37AM +0200, Jani Nikula wrote:
> On Thu, 23 Jan 2020, "Bharadiya,Pankaj" <pankaj.laxminarayan.bharadiya@intel.com> 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 have in i915_utils.h.
Still i915 driver wil have many calls to WARN_ON* after this patch
series gets merged.
Shall I remove WARN_ON/WARN_ON_ONCE "overrides" so that existing
callers will fallback to original WARN_ON* implementation until
complete conversion is done? Just want to double confirm on this
before I submit a patch.
Thanks,
Pankaj
>
> Thanks,
> Jani.
>
> --
> Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-01-27 8:26 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 3:44 [[Intel-gfx] [PATCH v2 00/10] drm: Introduce struct drm_device based WARN* and use them in i915 Pankaj Bharadiya
2020-01-15 3:44 ` [Intel-gfx] [ " Pankaj Bharadiya
2020-01-15 3:44 ` [[Intel-gfx] [PATCH v2 01/10] drm/print: introduce new struct drm_device based WARN* macros Pankaj Bharadiya
2020-01-15 3:44 ` [Intel-gfx] [ " Pankaj Bharadiya
2020-01-15 10:02 ` [[Intel-gfx] " Jani Nikula
2020-01-15 10:02 ` [Intel-gfx] [ " Jani Nikula
2020-01-21 8:39 ` [[Intel-gfx] " Jani Nikula
2020-01-21 8:39 ` [Intel-gfx] [ " Jani Nikula
2020-01-21 9:13 ` [[Intel-gfx] " Sam Ravnborg
2020-01-21 9:13 ` [Intel-gfx] [ " Sam Ravnborg
2020-01-22 13:30 ` Sean Paul
2020-01-22 13:30 ` Sean Paul
2020-01-22 15:32 ` Jani Nikula
2020-01-22 15:32 ` Jani Nikula
2020-01-15 3:44 ` [[Intel-gfx] [PATCH v2 02/10] drm/i915/display: Make WARN* drm specific where drm_device ptr is available Pankaj Bharadiya
2020-01-15 3:44 ` [Intel-gfx] [ " Pankaj Bharadiya
2020-01-15 3:44 ` [[Intel-gfx] [PATCH v2 03/10] drm/i915/display: Make WARN* drm specific where drm_priv " Pankaj Bharadiya
2020-01-15 3:44 ` [Intel-gfx] [ " Pankaj Bharadiya
2020-01-15 3:44 ` [[Intel-gfx] [PATCH v2 04/10] drm/i915/display: Make WARN* drm specific where encoder " Pankaj Bharadiya
2020-01-15 3:44 ` [Intel-gfx] [ " Pankaj Bharadiya
2020-01-15 3:44 ` [[Intel-gfx] [PATCH v2 05/10] drm/i915/gem: Make WARN* drm specific where drm_priv " Pankaj Bharadiya
2020-01-15 3:44 ` [Intel-gfx] [ " Pankaj Bharadiya
2020-01-15 3:44 ` [[Intel-gfx] [PATCH v2 06/10] drm/i915/gt: " Pankaj Bharadiya
2020-01-15 3:44 ` [Intel-gfx] [ " Pankaj Bharadiya
2020-01-15 3:44 ` [[Intel-gfx] [PATCH v2 07/10] drm/i915/gvt: " Pankaj Bharadiya
2020-01-15 3:44 ` [Intel-gfx] [ " Pankaj Bharadiya
2020-01-15 3:44 ` [[Intel-gfx] [PATCH v2 08/10] drm/i915/gvt: Make WARN* drm specific where vgpu " Pankaj Bharadiya
2020-01-15 3:44 ` [Intel-gfx] [ " Pankaj Bharadiya
2020-01-15 3:44 ` [[Intel-gfx] [PATCH v2 09/10] drm/i915: Make WARN* drm specific where drm_priv " Pankaj Bharadiya
2020-01-15 3:44 ` [Intel-gfx] [ " Pankaj Bharadiya
2020-01-15 3:44 ` [[Intel-gfx] [PATCH v2 10/10] drm/i915: Make WARN* drm specific where uncore or stream " Pankaj Bharadiya
2020-01-15 3:44 ` [Intel-gfx] [ " Pankaj Bharadiya
2020-01-15 4:11 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm: Introduce struct drm_device based WARN* and use them in i915 (rev2) Patchwork
2020-01-15 4:38 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-01-15 4:38 ` [Intel-gfx] ✗ Fi.CI.BUILD: warning " Patchwork
2020-01-17 11:31 ` [Intel-gfx] ✓ Fi.CI.IGT: success " Patchwork
2020-01-22 16:22 ` [[Intel-gfx] [PATCH v2 00/10] drm: Introduce struct drm_device based WARN* and use them in i915 Jani Nikula
2020-01-22 16:22 ` [Intel-gfx] [ " Jani Nikula
2020-01-23 9:00 ` [[Intel-gfx] " Bharadiya,Pankaj
2020-01-23 9:00 ` [Intel-gfx] [ " Bharadiya,Pankaj
2020-01-23 9:39 ` [[Intel-gfx] " Jani Nikula
2020-01-23 9:39 ` [Intel-gfx] [ " Jani Nikula
2020-01-27 8:14 ` Bharadiya,Pankaj [this message]
2020-01-27 8:14 ` Bharadiya,Pankaj
2020-01-27 9:01 ` [[Intel-gfx] " Jani Nikula
2020-01-27 9:01 ` [Intel-gfx] [ " Jani Nikula
-- strict thread matches above, loose matches on Subject: below --
2020-01-15 3:43 [[Intel-gfx] " Pankaj Bharadiya
2020-01-15 3:43 ` [Intel-gfx] [ " Pankaj Bharadiya
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=20200127081423.GB8711@plaxmina-desktop.iind.intel.com \
--to=pankaj.laxminarayan.bharadiya@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=sam@ravnborg.org \
--cc=sudeep.dutt@intel.com \
/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.