Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mitul Golani <mitulkumar.ajitkumar.golani@intel.com>
Cc: dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
	ankit.k.nautiyal@intel.com, jani.nikula@intel.com
Subject: Re: [PATCH] drm/dp: correct struct member name in documentation
Date: Fri, 5 Apr 2024 19:29:54 +1100	[thread overview]
Message-ID: <20240405192954.492f863a@canb.auug.org.au> (raw)
In-Reply-To: <20240405065159.439145-1-mitulkumar.ajitkumar.golani@intel.com>

[-- Attachment #1: Type: text/plain, Size: 622 bytes --]

Hi Mitul,

Thanks.

On Fri,  5 Apr 2024 12:21:59 +0530 Mitul Golani <mitulkumar.ajitkumar.golani@intel.com> wrote:
>
> Correct struct member name to 'mode' instead of 'operation mode'
> in 'drm_dp_as_sdp' structure description.
> 
> Fixes: 0bbb8f594e33 ("drm/dp: Add Adaptive Sync SDP logging")

Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>

> Cc: Mitul Golani <mitulkumar.ajitkumar.golani@intel.com>
> Cc: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Signed-off-by: Mitul Golani <mitulkumar.ajitkumar.golani@intel.com>

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2024-04-05  8:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05  6:51 [PATCH] drm/dp: correct struct member name in documentation Mitul Golani
2024-04-05  7:50 ` ✗ Fi.CI.SPARSE: warning for " Patchwork
2024-04-05  8:00 ` [PATCH] " Dmitry Baryshkov
2024-04-05  8:01 ` ✗ Fi.CI.BAT: failure for " Patchwork
2024-04-05  8:29 ` Stephen Rothwell [this message]
2024-04-05 18:46 ` ✓ Fi.CI.BAT: success " Patchwork
2024-04-06  0:01 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-04-10 16:19 ` [PATCH] " Rodrigo Vivi
2024-04-11 16:55   ` Golani, Mitulkumar Ajitkumar
2024-04-16 21:31     ` Rodrigo Vivi

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=20240405192954.492f863a@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=ankit.k.nautiyal@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=mitulkumar.ajitkumar.golani@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