public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Ben Widawsky <ben@bwidawsk.net>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: rip out intel_dpio_write again
Date: Wed, 2 May 2012 13:18:56 -0700	[thread overview]
Message-ID: <20120502131856.5375aa47@bwidawsk.net> (raw)
In-Reply-To: <20120502115548.0cecafac@jbarnes-desktop>

On Wed, 2 May 2012 11:55:48 -0700
Jesse Barnes <jbarnes@virtuousgeek.org> wrote:

> On Wed, 2 May 2012 08:44:27 -0700
> Ben Widawsky <ben@bwidawsk.net> wrote:
> 
> > On Wed,  2 May 2012 11:06:23 +0200
> > Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> > 
> > > Unfortunately it looks like further vlv patches are still stalled due
> > > to fried hw, and too many people are a bit annoyed about the unused
> > > function warning.
> > 
> > It is my preference that you never merge code which you know will
> > produce a warning. I still stand by adding a __used for intermediate
> > patches.
> 
> Well he could have just merged the other patches too, but nooo...
> 

Twasn't a shot at you... shot was fired at Daniel (although if you *did*
but in __used I wouldn't have had to shoot at Daniel).


-- 
Ben Widawsky, Intel Open Source Technology Center

  reply	other threads:[~2012-05-02 20:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-02  9:06 [PATCH] drm/i915: rip out intel_dpio_write again Daniel Vetter
2012-05-02 15:44 ` Ben Widawsky
2012-05-02 18:55   ` Jesse Barnes
2012-05-02 20:18     ` Ben Widawsky [this message]
2012-05-03  0:22       ` Jesse Barnes
2012-05-03  9:10         ` Daniel Vetter

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=20120502131856.5375aa47@bwidawsk.net \
    --to=ben@bwidawsk.net \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jbarnes@virtuousgeek.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox