From: Thierry Reding <thierry.reding@gmail.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/scdc-helper: Remove gratuitous blank lines
Date: Fri, 1 Sep 2017 21:03:32 +0200 [thread overview]
Message-ID: <20170901190332.GA20593@ulmo> (raw)
In-Reply-To: <20170901160052.GZ4914@intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 501 bytes --]
On Fri, Sep 01, 2017 at 07:00:52PM +0300, Ville Syrjälä wrote:
> On Fri, Sep 01, 2017 at 04:44:28PM +0200, Thierry Reding wrote:
> > From: Thierry Reding <treding@nvidia.com>
> >
> > It's unusual to separate kerneldoc comments from the functions that they
> > describe by a blank line. Remove them.
> >
> > Signed-off-by: Thierry Reding <treding@nvidia.com>
>
> Series lgtm
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Applied to drm-misc-next, thanks.
Thierry
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-09-01 19:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 14:44 [PATCH 1/3] drm/scdc-helper: Remove gratuitous blank lines Thierry Reding
2017-09-01 14:44 ` [PATCH 2/3] drm/scdc-helper: Use consistent error reporting Thierry Reding
2017-09-04 9:14 ` Sharma, Shashank
2017-09-01 14:44 ` [PATCH 3/3] drm/scdc-helper: Use consistent spelling for TMDS Thierry Reding
2017-09-04 9:16 ` Sharma, Shashank
2017-09-01 16:00 ` [PATCH 1/3] drm/scdc-helper: Remove gratuitous blank lines Ville Syrjälä
2017-09-01 19:03 ` Thierry Reding [this message]
2017-09-04 9:13 ` Sharma, Shashank
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=20170901190332.GA20593@ulmo \
--to=thierry.reding@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--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 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.