GNU/Weeb Mailing List <[email protected]>
 help / color / mirror / Atom feed
From: kernel test robot <[email protected]>
To: Ammar Faizi <[email protected]>,
	GNU/Weeb Mailing List <[email protected]>
Cc: [email protected]
Subject: [ammarfaizi2-block:google/android/kernel/common/android-4.19-stable 543/9999] drivers/gpu/drm/drm_dp_mst_topology.c:1843 drm_dp_mst_update_dsc_info() warn: inconsistent indenting
Date: Thu, 2 Mar 2023 21:36:35 +0800	[thread overview]
Message-ID: <[email protected]> (raw)

tree:   https://github.com/ammarfaizi2/linux-block google/android/kernel/common/android-4.19-stable
head:   ef8b9b38090e63de841d55b568aa5f60c587f14c
commit: b572376bedc67f334d005dabd7727dd318eeba44 [543/9999] ANDROID: GKI: Add 'dsc_info' to struct drm_dp_mst_port
config: i386-randconfig-m021 (https://download.01.org/0day-ci/archive/20230302/[email protected]/config)
compiler: gcc-11 (Debian 11.3.0-8) 11.3.0

If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <[email protected]>
| Link: https://lore.kernel.org/oe-kbuild-all/[email protected]/

smatch warnings:
drivers/gpu/drm/drm_dp_mst_topology.c:1843 drm_dp_mst_update_dsc_info() warn: inconsistent indenting

vim +1843 drivers/gpu/drm/drm_dp_mst_topology.c

  1830	
  1831	int drm_dp_mst_update_dsc_info(struct drm_dp_mst_topology_mgr *mgr,
  1832			struct drm_dp_mst_port *port,
  1833			struct drm_dp_mst_dsc_info *dsc_info)
  1834	{
  1835		if (!dsc_info)
  1836			return -EINVAL;
  1837	
  1838		port = drm_dp_get_validated_port_ref(mgr, port);
  1839		if (!port)
  1840			return -EINVAL;
  1841	
  1842		memcpy(&port->dsc_info, dsc_info, sizeof(struct drm_dp_mst_dsc_info));
> 1843			drm_dp_put_port(port);
  1844	
  1845		return 0;
  1846	}
  1847	EXPORT_SYMBOL_GPL(drm_dp_mst_update_dsc_info);
  1848	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests

                 reply	other threads:[~2023-03-02 13:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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