All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
	Eric Engestrom <eric.engestrom@imgtec.com>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH] drm: drm_printer: add __printf validation
Date: Tue, 21 Feb 2017 00:32:59 -0800	[thread overview]
Message-ID: <1487665979.2853.16.camel@perches.com> (raw)
In-Reply-To: <87a89gkl09.fsf@intel.com>

On Tue, 2017-02-21 at 10:26 +0200, Jani Nikula wrote:
> You know how this stuff works, please split it up to get the stuff
> merged.

Quite well actually.

Fix it as you think appropriate.
But in any case, fix it.
_______________________________________________
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: Joe Perches <joe@perches.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
	Eric Engestrom <eric.engestrom@imgtec.com>
Cc: Rob Clark <robdclark@gmail.com>,
	Daniel Vetter <daniel.vetter@intel.com>,
	Sean Paul <seanpaul@chromium.org>,
	David Airlie <airlied@linux.ie>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm: drm_printer: add __printf validation
Date: Tue, 21 Feb 2017 00:32:59 -0800	[thread overview]
Message-ID: <1487665979.2853.16.camel@perches.com> (raw)
In-Reply-To: <87a89gkl09.fsf@intel.com>

On Tue, 2017-02-21 at 10:26 +0200, Jani Nikula wrote:
> You know how this stuff works, please split it up to get the stuff
> merged.

Quite well actually.

Fix it as you think appropriate.
But in any case, fix it.

  reply	other threads:[~2017-02-21  8:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-15 23:33 [PATCH] drm: drm_printer: add __printf validation Joe Perches
2017-02-20 12:17 ` Eric Engestrom
2017-02-20 12:17   ` Eric Engestrom
2017-02-20 17:10   ` Joe Perches
2017-02-20 17:10     ` Joe Perches
2017-02-21  8:26     ` Jani Nikula
2017-02-21  8:26       ` Jani Nikula
2017-02-21  8:32       ` Joe Perches [this message]
2017-02-21  8:32         ` Joe Perches
2017-02-21  9:02         ` Jani Nikula
2017-02-21  9:02           ` Jani Nikula
2017-02-21  9:18           ` Joe Perches
2017-02-21  9:18             ` Joe Perches
2017-02-26 20:43             ` 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=1487665979.2853.16.camel@perches.com \
    --to=joe@perches.com \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=eric.engestrom@imgtec.com \
    --cc=jani.nikula@linux.intel.com \
    --cc=linux-kernel@vger.kernel.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.