From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/i915: Silence sparse by using gfp_t
Date: Mon, 18 Sep 2017 16:19:42 +0300 [thread overview]
Message-ID: <1505740782.14048.47.camel@linux.intel.com> (raw)
In-Reply-To: <150452330931.23157.9805901080313906604@mail.alporthouse.com>
On Mon, 2017-09-04 at 12:08 +0100, Chris Wilson wrote:
> Quoting Joonas Lahtinen (2017-09-04 07:50:38)
> > On Fri, 2017-09-01 at 15:57 +0100, Chris Wilson wrote:
> > > Sparse enforces that GFP flags are only manipulated inside gfp_t locals.
> > >
> > > Fixes: 4d470f7359c4 ("drm/i915: Avoid undefined behaviour of "u32 >> 32"")
> > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > > Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> > > Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> >
> > Isn't Fixes: bit much for sparse warning?
>
> Impact: None ?
Well, "Impact: Cosmetic" would be more truthful but complex.
"Backport: None" ?
Could also take the value that is currently causing grief in the Cc:
stable line;
"Backport: v4.8+"
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-09-18 13:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 14:57 [PATCH 1/2] drm/i915: Silence sparse by using gfp_t Chris Wilson
2017-09-01 14:57 ` [PATCH 2/2] drm/i915/perf: Remove __user from u64 in drm_i915_perf_oa_config Chris Wilson
2017-09-01 15:05 ` Lionel Landwerlin
2017-09-01 15:21 ` [PATCH 1/2] drm/i915: Silence sparse by using gfp_t Ville Syrjälä
2017-09-01 15:47 ` ✗ Fi.CI.BAT: failure for series starting with [1/2] " Patchwork
2017-09-04 6:50 ` [PATCH 1/2] " Joonas Lahtinen
2017-09-04 11:08 ` Chris Wilson
2017-09-18 13:19 ` Joonas Lahtinen [this message]
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=1505740782.14048.47.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
/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.