From: Jani Nikula <jani.nikula@linux.intel.com>
To: Nathan Chancellor <natechancellor@gmail.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: "Michel Dänzer" <michel@daenzer.net>,
LKML <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
clang-built-linux <clang-built-linux@googlegroups.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Cast remain to unsigned long in eb_relocate_vma
Date: Fri, 27 Mar 2020 00:15:09 +0200 [thread overview]
Message-ID: <87r1xehifm.fsf@intel.com> (raw)
In-Reply-To: <20200326201158.GA30083@ubuntu-m2-xlarge-x86>
On Thu, 26 Mar 2020, Nathan Chancellor <natechancellor@gmail.com> wrote:
> This is the only warning on an x86_64 defconfig build. Apologies if we
> are being too persistent or nagging but we need guidance from the i915
> maintainers on which solution they would prefer so it can be picked up.
> I understand you all are busy and I appreciate the work you all do but
> I do not want this to fall between the cracks because it is annoying to
> constantly see this warning.
Apologies for the delay. As I replied first thing in this thread, this
works for me. Thanks for the patch, pushed to drm-intel-next-queued.
BR,
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: Jani Nikula <jani.nikula@linux.intel.com>
To: Nathan Chancellor <natechancellor@gmail.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: "Michel Dänzer" <michel@daenzer.net>,
LKML <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
clang-built-linux <clang-built-linux@googlegroups.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Cast remain to unsigned long in eb_relocate_vma
Date: Fri, 27 Mar 2020 00:15:09 +0200 [thread overview]
Message-ID: <87r1xehifm.fsf@intel.com> (raw)
In-Reply-To: <20200326201158.GA30083@ubuntu-m2-xlarge-x86>
On Thu, 26 Mar 2020, Nathan Chancellor <natechancellor@gmail.com> wrote:
> This is the only warning on an x86_64 defconfig build. Apologies if we
> are being too persistent or nagging but we need guidance from the i915
> maintainers on which solution they would prefer so it can be picked up.
> I understand you all are busy and I appreciate the work you all do but
> I do not want this to fall between the cracks because it is annoying to
> constantly see this warning.
Apologies for the delay. As I replied first thing in this thread, this
works for me. Thanks for the patch, pushed to drm-intel-next-queued.
BR,
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
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Nathan Chancellor <natechancellor@gmail.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: "Michel Dänzer" <michel@daenzer.net>,
"Chris Wilson" <chris@chris-wilson.co.uk>,
intel-gfx@lists.freedesktop.org,
LKML <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
clang-built-linux <clang-built-linux@googlegroups.com>
Subject: Re: [PATCH] drm/i915: Cast remain to unsigned long in eb_relocate_vma
Date: Fri, 27 Mar 2020 00:15:09 +0200 [thread overview]
Message-ID: <87r1xehifm.fsf@intel.com> (raw)
In-Reply-To: <20200326201158.GA30083@ubuntu-m2-xlarge-x86>
On Thu, 26 Mar 2020, Nathan Chancellor <natechancellor@gmail.com> wrote:
> This is the only warning on an x86_64 defconfig build. Apologies if we
> are being too persistent or nagging but we need guidance from the i915
> maintainers on which solution they would prefer so it can be picked up.
> I understand you all are busy and I appreciate the work you all do but
> I do not want this to fall between the cracks because it is annoying to
> constantly see this warning.
Apologies for the delay. As I replied first thing in this thread, this
works for me. Thanks for the patch, pushed to drm-intel-next-queued.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2020-03-26 22:15 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 5:47 [PATCH] drm/i915: Cast remain to unsigned long in eb_relocate_vma Nathan Chancellor
2020-02-14 5:47 ` Nathan Chancellor
2020-02-14 5:47 ` [Intel-gfx] " Nathan Chancellor
2020-02-14 6:31 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-02-14 6:36 ` [PATCH] " Jani Nikula
2020-02-14 6:36 ` Jani Nikula
2020-02-14 6:36 ` [Intel-gfx] " Jani Nikula
2020-02-14 8:32 ` Chris Wilson
2020-02-14 8:32 ` Chris Wilson
2020-02-14 8:32 ` [Intel-gfx] " Chris Wilson
2020-02-14 11:49 ` Jani Nikula
2020-02-14 11:49 ` Jani Nikula
2020-02-14 11:49 ` [Intel-gfx] " Jani Nikula
2020-02-14 15:36 ` Michel Dänzer
2020-02-14 15:36 ` Michel Dänzer
2020-02-14 15:36 ` [Intel-gfx] " Michel Dänzer
2020-03-16 21:41 ` Nick Desaulniers
2020-03-16 21:41 ` Nick Desaulniers
2020-03-16 21:41 ` [Intel-gfx] " Nick Desaulniers
2020-03-26 20:11 ` Nathan Chancellor
2020-03-26 20:11 ` Nathan Chancellor
2020-03-26 20:11 ` [Intel-gfx] " Nathan Chancellor
2020-03-26 22:15 ` Jani Nikula [this message]
2020-03-26 22:15 ` Jani Nikula
2020-03-26 22:15 ` [Intel-gfx] " Jani Nikula
2020-02-14 13:46 ` Nathan Chancellor
2020-02-14 13:46 ` Nathan Chancellor
2020-02-14 13:46 ` [Intel-gfx] " Nathan Chancellor
2020-02-17 17:06 ` [Intel-gfx] ✓ Fi.CI.IGT: success for " Patchwork
2020-03-17 0:13 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915: Cast remain to unsigned long in eb_relocate_vma (rev2) Patchwork
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=87r1xehifm.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=clang-built-linux@googlegroups.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michel@daenzer.net \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=rodrigo.vivi@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.