public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: "Singh, Gaurav K" <gaurav.k.singh@intel.com>
Cc: Shobhit Kumar <shobhit.kumar@intel.com>,
	intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 02/10] drm/i915: Added port as parameter to the	functions which does read/write of DSI Controller
Date: Fri, 5 Dec 2014 15:38:46 +0100	[thread overview]
Message-ID: <20141205143846.GP20350@phenom.ffwll.local> (raw)
In-Reply-To: <5481AA23.80308@intel.com>

On Fri, Dec 05, 2014 at 06:20:43PM +0530, Singh, Gaurav K wrote:
> 
> On 12/4/2014 4:52 PM, Daniel Vetter wrote:
> >On Thu, Dec 04, 2014 at 11:14:01AM +0200, Jani Nikula wrote:
> >>On Thu, 04 Dec 2014, Gaurav K Singh <gaurav.k.singh@intel.com> wrote:
> >>>This patch is in preparation of DSI dual link panels. For dual link
> >>>panels, few packets needs to be sent to Port A or Port C or both. Based
> >>>on the portno from MIPI Sequence Block#53, these sequences needs to be
> >>>sent accordingly.
> >>>
> >>>v2: Addressed review comments by Jani
> >>>     - port variables named properly
> >>>
> >>>Signed-off-by: Gaurav K Singh <gaurav.k.singh@intel.com>
> >>Reviewed-by: Jani Nikula <jani.nikula@intel.com>
> >Merged the first two patches, thanks.
> >-Daniel
> Hi Daniel,
> 
> Thanks. I have addressed Jani's review comments too for the rest of the
> patches.

Well looking through the resend patches your changes look a bit minimal.
Which might be the right thing to do, but review is also about
communication and sharing expert knowledge. So please follow up to the
questions from Jani where you didn't adjust the code. And if there's any
follow-up patches from those discussions please submit them.

Another part: Your editor doesn't seem to align continuation lines quite
how we usually do that. checkpatch --strict will catch that. Two big
rules:
- function paramater lists should be aligned to the opening ( on the next
  line.
- Continuations of boolean logic checks (e.g. in if checks) same, with the
  special rule that && or || should be on the previous line as the last
  thing.
- continuation of any other long lines should be indented 1 or two spaces
  (just to make sure it sticks out without looking jarring).

Especially the first two help readability a lot of you're used to them, so
please do a follow-up patch to rectify this in intel_dsi*.c.

Thanks, Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2014-12-05 14:38 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-04  5:28 [PATCH 00/10] BYT DSI Dual Link Support Gaurav K Singh
2014-12-04  5:28 ` [PATCH 01/10] drm/i915: New functions added for enabling & disabling MIPI Port Ctrl reg Gaurav K Singh
2014-12-04  9:13   ` Jani Nikula
2014-12-04  5:28 ` [PATCH 02/10] drm/i915: Added port as parameter to the functions which does read/write of DSI Controller Gaurav K Singh
2014-12-04  9:14   ` Jani Nikula
2014-12-04 11:22     ` Daniel Vetter
2014-12-05 12:50       ` Singh, Gaurav K
2014-12-05 14:38         ` Daniel Vetter [this message]
2014-12-05 20:35           ` Singh, Gaurav K
2014-12-04  5:28 ` [PATCH 03/10] drm/i915: Add support for port enable/disable for dual link configuration Gaurav K Singh
2014-12-04  9:17   ` Jani Nikula
2014-12-05  8:39     ` [PATCH v4 " Gaurav K Singh
2014-12-05 12:52       ` Jani Nikula
2014-12-04  5:28 ` [PATCH 04/10] drm/i915: Pixel Clock changes for DSI dual link Gaurav K Singh
2014-12-04  9:27   ` Jani Nikula
2014-12-05  8:43     ` [PATCH v3 " Gaurav K Singh
2014-12-05 16:33     ` [PATCH " Singh, Gaurav K
2014-12-05 16:54       ` Siluvery, Arun
2014-12-05 17:18         ` Singh, Gaurav K
2014-12-05 17:36         ` Jani Nikula
2014-12-05 17:48           ` Siluvery, Arun
2014-12-05 20:43             ` Singh, Gaurav K
2014-12-04  5:28 ` [PATCH 05/10] drm/i915: Dual link needs Shutdown and Turn on packet for both ports Gaurav K Singh
2014-12-04 10:41   ` Jani Nikula
2014-12-05 19:10     ` [PATCH 5/5] " Gaurav K Singh
2014-12-05 20:53       ` Daniel Vetter
2014-12-04  5:28 ` [PATCH 06/10] drm/i915: Enable DSI PLL for both DSI0 and DSI1 in case of dual link Gaurav K Singh
2014-12-04 11:17   ` Jani Nikula
2014-12-04  5:28 ` [PATCH 07/10] drm/i915: cck reg used for checking DSI Pll locked Gaurav K Singh
2014-12-04 11:22   ` Jani Nikula
2014-12-05  8:46     ` [PATCH v2 " Gaurav K Singh
2014-12-04  5:28 ` [PATCH 08/10] drm/i915: MIPI Timings related changes for dual link Gaurav K Singh
2014-12-04 11:24   ` Jani Nikula
2014-12-04  5:28 ` [PATCH 09/10] drm/i915: Update the DSI disable path to support dual link panel disabling Gaurav K Singh
2014-12-04 11:37   ` Jani Nikula
2014-12-05  8:52     ` [PATCH v4 " Gaurav K Singh
2014-12-04  5:28 ` [PATCH 10/10] drm/i915: Update the DSI enable path to support dual link panel enabling Gaurav K Singh
2014-12-04 11:49   ` Jani Nikula
2014-12-05  8:54     ` [PATCH v4 10/10] drm/i915: Update the DSI enable path to support dual Gaurav K Singh
2014-12-05 20:31       ` [PATCH " Gaurav K Singh
2014-12-05  4:04   ` [PATCH 10/10] drm/i915: Update the DSI enable path to support dual link panel enabling 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=20141205143846.GP20350@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=gaurav.k.singh@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=shobhit.kumar@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