From: Daniel Vetter <daniel@ffwll.ch>
To: "Chris Wilson" <chris@chris-wilson.co.uk>,
"Jani Nikula" <jani.nikula@intel.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/3] drm/i915: add yesno utility function
Date: Wed, 2 Sep 2015 11:17:49 +0200 [thread overview]
Message-ID: <20150902091749.GN1367@phenom.ffwll.local> (raw)
In-Reply-To: <20150831143313.GT17184@nuc-i3427.alporthouse.com>
On Mon, Aug 31, 2015 at 03:33:13PM +0100, Chris Wilson wrote:
> On Mon, Aug 31, 2015 at 05:23:27PM +0300, Jani Nikula wrote:
> > On Thu, 27 Aug 2015, Jani Nikula <jani.nikula@intel.com> wrote:
> > > On Thu, 27 Aug 2015, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> > >> On Thu, Aug 27, 2015 at 04:23:30PM +0300, Jani Nikula wrote:
> > >>> Add a common function to return "yes" or "no" string based on the
> > >>> argument, and drop the local versions of it.
> > >>
> > >> Purely out of curiosity, gcc is able to amalgamate the constant strings
> > >> (I remember reading that it is intelligent enough to do so), right? i.e.
> > >> size i915.ko doesn't change (at least .data, we may see .text
> > >> differences for gcc having different ideas about inlines)?
> > >
> > > I admit to giving GCC the benefit of the doubt. I may be naïve that way,
> > > trusting the tools to do what seems like the obviously right thing to
> > > do.
> > >
> > > If GCC lets us down, we could try something like the yesno version in
> > > drivers/net/ethernet/chelsio/cxgb4/cxgb4_debugfs.c. GCC not doing the
> > > right thing with that would be violating the standard.
> >
> > AFAICT GCC does the right thing with the patch.
>
> Fwiw, I didn't see any harm in the series, so
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Merged just this patch (due to conflict fun for now) to dinq, thanks.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-09-02 9:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 10:25 [PATCH v2 1/3] i915/dp: add intel_dp_tps3_supported helper Jani Nikula
2015-08-27 10:25 ` [PATCH v2 2/3] drm/i915/dp: use the drm dp helper for determining sink tps3 support Jani Nikula
2015-09-01 9:37 ` Daniel Vetter
2015-09-03 8:20 ` Jani Nikula
2015-08-27 10:25 ` [PATCH v2 3/3] drm/i915/dp: move TPS3 logic to where it's used Jani Nikula
2015-08-27 12:15 ` Ville Syrjälä
2015-08-27 13:23 ` [PATCH 0/3] follow-up Jani Nikula
2015-08-27 13:23 ` [PATCH 1/3] drm/i915: ignore link rate in TPS3 selection Jani Nikula
2015-08-27 13:23 ` [PATCH 2/3] drm/i915: add yesno utility function Jani Nikula
2015-08-27 13:28 ` Chris Wilson
2015-08-27 13:53 ` Jani Nikula
2015-08-31 14:23 ` Jani Nikula
2015-08-31 14:33 ` Chris Wilson
2015-09-02 9:17 ` Daniel Vetter [this message]
2015-08-27 13:23 ` [PATCH 3/3] drm/i915: use the yesno helper for logging Jani Nikula
2015-08-29 19:00 ` [PATCH v2 3/3] drm/i915/dp: move TPS3 logic to where it's used shuang.he
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=20150902091749.GN1367@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=ville.syrjala@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox