From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Damien Lespiau <damien.lespiau@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/i915: Use seq_puts/seq_putc when possible
Date: Tue, 25 Jun 2013 13:32:52 +0300 [thread overview]
Message-ID: <20130625103252.GN5004@intel.com> (raw)
In-Reply-To: <1372111190-5193-1-git-send-email-damien.lespiau@intel.com>
On Mon, Jun 24, 2013 at 10:59:48PM +0100, Damien Lespiau wrote:
> Caught with checkpatch.pl.
>
> Suggested-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
For the series:
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2013-06-25 10:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 21:59 [PATCH 1/3] drm/i915: Use seq_puts/seq_putc when possible Damien Lespiau
2013-06-24 21:59 ` [PATCH 2/3] drm/i915: Fix a few style issues found by checkpatch.pl Damien Lespiau
2013-06-24 21:59 ` [PATCH 3/3] drm/i915: Fix a couple of "should it be static?" sparse warnings Damien Lespiau
2013-06-25 10:32 ` Ville Syrjälä [this message]
2013-06-25 12:38 ` [PATCH 1/3] drm/i915: Use seq_puts/seq_putc when possible 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=20130625103252.GN5004@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=damien.lespiau@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox