All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lucas De Marchi <lucas.demarchi@intel.com>
To: Mullati Siva <siva.mullati@intel.com>
Cc: jani.nikula@intel.com, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Skip remap_io_mapping() for non-x86 platforms
Date: Wed, 8 Dec 2021 13:26:10 -0800	[thread overview]
Message-ID: <20211208212610.vha6jfmnoh674kqg@ldmartin-desk2> (raw)
In-Reply-To: <20211208041215.763098-1-siva.mullati@intel.com>

On Wed, Dec 08, 2021 at 09:42:15AM +0530, Mullati Siva wrote:
>From: Siva Mullati <siva.mullati@intel.com>
>
>Only hw that supports mappable aperture would hit this path
>vm_fault_gtt/vm_fault_tmm, So we never hit this function
>remap_io_mapping() in discrete, So skip this code for non-x86
>architectures.
>
>v2: use IS_ENABLED () instead of #if defined
>
>v3: move function prototypes from i915_drv.h to i915_mm.h
>
>v4: added kernel error message in stub function
>
>v5: fixed compilation warnings
>
>v6: checkpatch style
>
>Signed-off-by: Siva Mullati <siva.mullati@intel.com>

the change in gem/ is just adding the additional include - looking at
the other changes, drm-intel-next seems a better place to merge this
since it can be considered as part of the i915_drv.h cleanup going on.

Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com>

and applied, thanks.

Lucas De Marchi

  parent reply	other threads:[~2021-12-08 21:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-08  4:12 [Intel-gfx] [PATCH] drm/i915: Skip remap_io_mapping() for non-x86 platforms Mullati Siva
2021-12-08  4:33 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Skip remap_io_mapping() for non-x86 platforms (rev6) Patchwork
2021-12-08  4:34 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-12-08  5:16 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2021-12-08  5:55 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Skip remap_io_mapping() for non-x86 platforms (rev7) Patchwork
2021-12-08  5:56 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-12-08  6:35 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-12-08 12:50 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-12-08 21:26 ` Lucas De Marchi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-12-07 16:49 [Intel-gfx] [PATCH] drm/i915: Skip remap_io_mapping() for non-x86 platforms Mullati Siva
2021-12-01 11:32 Mullati Siva
2021-11-22 12:31 Mullati Siva
2021-11-30 19:17 ` Lucas De Marchi
2021-12-01  9:04   ` Jani Nikula
2021-11-12 17:18 Mullati Siva
2021-11-12 22:18 ` Jani Nikula
2021-11-13 17:34   ` Lucas De Marchi
2021-11-16 19:24     ` Matthew Auld
2021-11-12 13:24 Mullati Siva
2021-11-12 14:09 ` Jani Nikula

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=20211208212610.vha6jfmnoh674kqg@ldmartin-desk2 \
    --to=lucas.demarchi@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=siva.mullati@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.