From: Sean Anderson <sean.anderson@linux.dev>
To: kernel test robot <lkp@intel.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
dri-devel@lists.freedesktop.org
Cc: oe-kbuild-all@lists.linux.dev, David Airlie <airlied@gmail.com>,
linux-kernel@vger.kernel.org, Michal Simek <monstr@monstr.eu>,
linux-arm-kernel@lists.infradead.org,
Daniel Vetter <daniel@ffwll.ch>
Subject: Re: [PATCH 6/6] drm: zynqmp_dp: Add debugfs interface for compliance testing
Date: Mon, 18 Mar 2024 11:06:40 -0400 [thread overview]
Message-ID: <ce1190ad-27c2-4a16-b36f-442c0c419dcc@linux.dev> (raw)
In-Reply-To: <202403161704.ACHJdSJG-lkp@intel.com>
On 3/16/24 06:14, kernel test robot wrote:
> Hi Sean,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on v6.8]
> [cannot apply to drm-misc/drm-misc-next linus/master next-20240315]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
> And when submitting patch, we suggest to use '--base' as documented in
> https://git-scm.com/docs/git-format-patch#_base_tree_information]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Sean-Anderson/drm-zynqmp_dp-Downgrade-log-level-for-aux-retries-message/20240316-071208
> base: v6.8
> patch link: https://lore.kernel.org/r/20240315230916.1759060-7-sean.anderson%40linux.dev
> patch subject: [PATCH 6/6] drm: zynqmp_dp: Add debugfs interface for compliance testing
> config: microblaze-allmodconfig (https://download.01.org/0day-ci/archive/20240316/202403161704.ACHJdSJG-lkp@intel.com/config)
> compiler: microblaze-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240316/202403161704.ACHJdSJG-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202403161704.ACHJdSJG-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> drivers/gpu/drm/xlnx/zynqmp_dp.c: In function 'zynqmp_dp_bridge_debugfs_init':
>>> drivers/gpu/drm/xlnx/zynqmp_dp.c:2168:31: warning: 'sprintf' may write a terminating nul past the end of the destination [-Wformat-overflow=]
> 2168 | sprintf(name, fmt, i);
> | ^~~
> drivers/gpu/drm/xlnx/zynqmp_dp.c:2168:17: note: 'sprintf' output between 18 and 20 bytes into a destination of size 19
> 2168 | sprintf(name, fmt, i);
> | ^~~~~~~~~~~~~~~~~~~~~
Not a bug, as i will be at most 4, which uses 1 digit.
--Sean
> vim +/sprintf +2168 drivers/gpu/drm/xlnx/zynqmp_dp.c
>
> 2136
> 2137 DEFINE_DEBUGFS_ATTRIBUTE(fops_zynqmp_dp_rate, zynqmp_dp_rate_get,
> 2138 zynqmp_dp_rate_set, "%llu\n");
> 2139
> 2140 static void zynqmp_dp_bridge_debugfs_init(struct drm_bridge *bridge,
> 2141 struct dentry *root)
> 2142 {
> 2143 struct zynqmp_dp *dp = bridge_to_dp(bridge);
> 2144 struct dentry *test;
> 2145 int i;
> 2146
> 2147 dp->test.bw_code = DP_LINK_BW_5_4;
> 2148 dp->test.link_cnt = dp->num_lanes;
> 2149
> 2150 test = debugfs_create_dir("test", root);
> 2151 #define CREATE_FILE(name) \
> 2152 debugfs_create_file(#name, 0600, test, dp, &fops_zynqmp_dp_##name)
> 2153 CREATE_FILE(pattern);
> 2154 CREATE_FILE(enhanced);
> 2155 CREATE_FILE(downspread);
> 2156 CREATE_FILE(active);
> 2157 CREATE_FILE(custom);
> 2158 CREATE_FILE(rate);
> 2159 CREATE_FILE(lanes);
> 2160
> 2161 for (i = 0; i < dp->num_lanes; i++) {
> 2162 static const char fmt[] = "lane%d_preemphasis";
> 2163 char name[sizeof(fmt)];
> 2164
> 2165 dp->debugfs_train_set[i].dp = dp;
> 2166 dp->debugfs_train_set[i].lane = i;
> 2167
>> 2168 sprintf(name, fmt, i);
> 2169 debugfs_create_file(name, 0600, test,
> 2170 &dp->debugfs_train_set[i],
> 2171 &fops_zynqmp_dp_preemphasis);
> 2172
> 2173 sprintf(name, "lane%d_swing", i);
> 2174 debugfs_create_file(name, 0600, test,
> 2175 &dp->debugfs_train_set[i],
> 2176 &fops_zynqmp_dp_swing);
> 2177 }
> 2178 }
> 2179
>
WARNING: multiple messages have this Message-ID (diff)
From: Sean Anderson <sean.anderson@linux.dev>
To: kernel test robot <lkp@intel.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
dri-devel@lists.freedesktop.org
Cc: oe-kbuild-all@lists.linux.dev, David Airlie <airlied@gmail.com>,
linux-kernel@vger.kernel.org, Michal Simek <monstr@monstr.eu>,
linux-arm-kernel@lists.infradead.org,
Daniel Vetter <daniel@ffwll.ch>
Subject: Re: [PATCH 6/6] drm: zynqmp_dp: Add debugfs interface for compliance testing
Date: Mon, 18 Mar 2024 11:06:40 -0400 [thread overview]
Message-ID: <ce1190ad-27c2-4a16-b36f-442c0c419dcc@linux.dev> (raw)
In-Reply-To: <202403161704.ACHJdSJG-lkp@intel.com>
On 3/16/24 06:14, kernel test robot wrote:
> Hi Sean,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on v6.8]
> [cannot apply to drm-misc/drm-misc-next linus/master next-20240315]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
> And when submitting patch, we suggest to use '--base' as documented in
> https://git-scm.com/docs/git-format-patch#_base_tree_information]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Sean-Anderson/drm-zynqmp_dp-Downgrade-log-level-for-aux-retries-message/20240316-071208
> base: v6.8
> patch link: https://lore.kernel.org/r/20240315230916.1759060-7-sean.anderson%40linux.dev
> patch subject: [PATCH 6/6] drm: zynqmp_dp: Add debugfs interface for compliance testing
> config: microblaze-allmodconfig (https://download.01.org/0day-ci/archive/20240316/202403161704.ACHJdSJG-lkp@intel.com/config)
> compiler: microblaze-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240316/202403161704.ACHJdSJG-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202403161704.ACHJdSJG-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> drivers/gpu/drm/xlnx/zynqmp_dp.c: In function 'zynqmp_dp_bridge_debugfs_init':
>>> drivers/gpu/drm/xlnx/zynqmp_dp.c:2168:31: warning: 'sprintf' may write a terminating nul past the end of the destination [-Wformat-overflow=]
> 2168 | sprintf(name, fmt, i);
> | ^~~
> drivers/gpu/drm/xlnx/zynqmp_dp.c:2168:17: note: 'sprintf' output between 18 and 20 bytes into a destination of size 19
> 2168 | sprintf(name, fmt, i);
> | ^~~~~~~~~~~~~~~~~~~~~
Not a bug, as i will be at most 4, which uses 1 digit.
--Sean
> vim +/sprintf +2168 drivers/gpu/drm/xlnx/zynqmp_dp.c
>
> 2136
> 2137 DEFINE_DEBUGFS_ATTRIBUTE(fops_zynqmp_dp_rate, zynqmp_dp_rate_get,
> 2138 zynqmp_dp_rate_set, "%llu\n");
> 2139
> 2140 static void zynqmp_dp_bridge_debugfs_init(struct drm_bridge *bridge,
> 2141 struct dentry *root)
> 2142 {
> 2143 struct zynqmp_dp *dp = bridge_to_dp(bridge);
> 2144 struct dentry *test;
> 2145 int i;
> 2146
> 2147 dp->test.bw_code = DP_LINK_BW_5_4;
> 2148 dp->test.link_cnt = dp->num_lanes;
> 2149
> 2150 test = debugfs_create_dir("test", root);
> 2151 #define CREATE_FILE(name) \
> 2152 debugfs_create_file(#name, 0600, test, dp, &fops_zynqmp_dp_##name)
> 2153 CREATE_FILE(pattern);
> 2154 CREATE_FILE(enhanced);
> 2155 CREATE_FILE(downspread);
> 2156 CREATE_FILE(active);
> 2157 CREATE_FILE(custom);
> 2158 CREATE_FILE(rate);
> 2159 CREATE_FILE(lanes);
> 2160
> 2161 for (i = 0; i < dp->num_lanes; i++) {
> 2162 static const char fmt[] = "lane%d_preemphasis";
> 2163 char name[sizeof(fmt)];
> 2164
> 2165 dp->debugfs_train_set[i].dp = dp;
> 2166 dp->debugfs_train_set[i].lane = i;
> 2167
>> 2168 sprintf(name, fmt, i);
> 2169 debugfs_create_file(name, 0600, test,
> 2170 &dp->debugfs_train_set[i],
> 2171 &fops_zynqmp_dp_preemphasis);
> 2172
> 2173 sprintf(name, "lane%d_swing", i);
> 2174 debugfs_create_file(name, 0600, test,
> 2175 &dp->debugfs_train_set[i],
> 2176 &fops_zynqmp_dp_swing);
> 2177 }
> 2178 }
> 2179
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-03-18 15:06 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 23:09 [PATCH 0/6] drm: zynqmp_dp: Misc. patches and debugfs support Sean Anderson
2024-03-15 23:09 ` Sean Anderson
2024-03-15 23:09 ` [PATCH 1/6] drm: zynqmp_dp: Downgrade log level for aux retries message Sean Anderson
2024-03-15 23:09 ` Sean Anderson
2024-03-18 16:39 ` Laurent Pinchart
2024-03-18 16:39 ` Laurent Pinchart
2024-03-15 23:09 ` [PATCH 2/6] drm: zynqmp_dp: Adjust training values per-lane Sean Anderson
2024-03-15 23:09 ` Sean Anderson
2024-03-18 17:06 ` Laurent Pinchart
2024-03-18 17:06 ` Laurent Pinchart
2024-03-15 23:09 ` [PATCH 3/6] drm: zynqmp_dp: Add locking Sean Anderson
2024-03-15 23:09 ` Sean Anderson
2024-03-16 9:52 ` kernel test robot
2024-03-16 9:52 ` kernel test robot
2024-03-18 15:09 ` Sean Anderson
2024-03-18 15:09 ` Sean Anderson
2024-03-18 17:16 ` Laurent Pinchart
2024-03-18 17:16 ` Laurent Pinchart
2024-03-18 17:29 ` Sean Anderson
2024-03-18 17:29 ` Sean Anderson
2024-03-18 17:59 ` Laurent Pinchart
2024-03-18 17:59 ` Laurent Pinchart
2024-03-18 18:01 ` Sean Anderson
2024-03-18 18:01 ` Sean Anderson
2024-03-15 23:09 ` [PATCH 4/6] drm: zynqmp_dp: Split off several helper functions Sean Anderson
2024-03-15 23:09 ` Sean Anderson
2024-03-18 17:41 ` Laurent Pinchart
2024-03-18 17:41 ` Laurent Pinchart
2024-03-15 23:09 ` [PATCH 5/6] drm: zynqmp_dp: Optionally ignore DPCD errors Sean Anderson
2024-03-15 23:09 ` Sean Anderson
2024-03-18 17:47 ` Laurent Pinchart
2024-03-18 17:47 ` Laurent Pinchart
2024-03-18 18:12 ` Sean Anderson
2024-03-18 18:12 ` Sean Anderson
2024-03-15 23:09 ` [PATCH 6/6] drm: zynqmp_dp: Add debugfs interface for compliance testing Sean Anderson
2024-03-15 23:09 ` Sean Anderson
2024-03-16 10:14 ` kernel test robot
2024-03-16 10:14 ` kernel test robot
2024-03-18 15:06 ` Sean Anderson [this message]
2024-03-18 15:06 ` Sean Anderson
2024-03-18 17:50 ` Laurent Pinchart
2024-03-18 17:50 ` Laurent Pinchart
2024-03-18 19:05 ` Sean Anderson
2024-03-18 19:05 ` Sean Anderson
2024-03-20 6:03 ` Yujie Liu
2024-03-20 6:03 ` Yujie Liu
2024-03-16 10:55 ` kernel test robot
2024-03-16 10:55 ` kernel test robot
2024-03-18 15:06 ` Sean Anderson
2024-03-18 15:06 ` Sean Anderson
2024-03-16 17:56 ` Dmitry Baryshkov
2024-03-16 17:56 ` Dmitry Baryshkov
2024-03-18 15:22 ` Sean Anderson
2024-03-18 15:22 ` Sean Anderson
2024-03-18 17:52 ` Laurent Pinchart
2024-03-18 17:52 ` Laurent Pinchart
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=ce1190ad-27c2-4a16-b36f-442c0c419dcc@linux.dev \
--to=sean.anderson@linux.dev \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=monstr@monstr.eu \
--cc=mripard@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--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 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.