public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kousik Sanagavarapu <five231003@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>
Subject: Re: [PATCH] gpu: drm: display: indent fix in comment
Date: Mon, 12 Feb 2024 19:44:36 +0530	[thread overview]
Message-ID: <ZconzKCU8CST45KF@five231003> (raw)
In-Reply-To: <7b17f021-cff8-4110-ac8f-c8f635263293@infradead.org>

On Sat, Feb 10, 2024 at 10:49:50PM -0800, Randy Dunlap wrote:
> 
> 
> On 2/8/24 07:20, Kousik Sanagavarapu wrote:
> > On Thu, Jan 25, 2024 at 12:05:56AM +0530, Kousik Sanagavarapu wrote:
> >> The comments explaining the function "drm_dp_mst_atom_check_mgr()" had
> >> uneven indentation which made "make htmldocs" complain:
> >>
> >> 	Documentation/gpu/drm-kms-helpers:296:
> >> 	./drivers/gpu/drm/display/drm_dp_mst_topology.c:5496:
> >> 	ERROR: Unexpected indentation.
> >>
> >> 	Documentation/gpu/drm-kms-helpers:296:
> >> 	./drivers/gpu/drm/display/drm_dp_mst_topology.c:5500:
> >> 	WARNING: Block quote ends without a blank line; unexpected unindent.
> >>
> >> Fix this by getting the indent right.
> >>
> >> Signed-off-by: Kousik Sanagavarapu <five231003@gmail.com>
> >> -- 
> > 
> > Ping again.
> > 
> > Thanks
> 
> Hi,
> This seems to be fixed by commit 1a84c213146a.

Makes sense.  Sorry for the noise.

> If you don't agree, please explain.
> Thanks.
> 
> -- 
> #Randy

      reply	other threads:[~2024-02-12 14:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-24 18:35 [PATCH] gpu: drm: display: indent fix in comment Kousik Sanagavarapu
2024-02-02 15:59 ` Kousik Sanagavarapu
2024-02-08 15:20 ` Kousik Sanagavarapu
2024-02-11  6:49   ` Randy Dunlap
2024-02-12 14:14     ` Kousik Sanagavarapu [this message]

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=ZconzKCU8CST45KF@five231003 \
    --to=five231003@gmail.com \
    --cc=airlied@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=rdunlap@infradead.org \
    --cc=tzimmermann@suse.de \
    /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