From: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>
To: "jiapeng.chong@linux.alibaba.com"
<jiapeng.chong@linux.alibaba.com>,
"jani.nikula@linux.intel.com" <jani.nikula@linux.intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"abaci@linux.alibaba.com" <abaci@linux.alibaba.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"daniel@ffwll.ch" <daniel@ffwll.ch>,
"airlied@gmail.com" <airlied@gmail.com>
Subject: Re: [Intel-gfx] [PATCH v2] drm/i915/hwconfig: Remove comment block
Date: Tue, 13 Dec 2022 13:33:36 +0000 [thread overview]
Message-ID: <3221542bbaf123525fa35a38bb1a4c5c1d0d292d.camel@intel.com> (raw)
In-Reply-To: <20221213055015.27968-1-jiapeng.chong@linux.alibaba.com>
On Tue, 2022-12-13 at 13:50 +0800, Jiapeng Chong wrote:
> No functional modification involved.
>
> drivers/gpu/drm/i915/gt/uc/intel_guc_hwconfig.c:112: warning:
> expecting prototype for intel_guc_hwconfig_init(). Prototype was for
> guc_hwconfig_init() instead.
Thank you for the patch and for addressing the comment.
But now the commit message is not explaining what's really going on.
Could you please improve the message saying that the function has
changed to static and we don't need doc comment in the static
functions, etc?!
Also, while doing this, please find a better commit message.
This is way to generic. Something like
drm/i915: Remove unnecessary doc from static hwconfig_init
sounds better and easier to understand from a log --oneline.
Oh, and it also looks this patch deserves a "Fixes:" tag,
pointing to the patch that created the mess. Either the original
patch if it already introduced like this, or to the patch that
transformed this function in static. git blame to find the culprit out.
With the commit msg fixed as above I will add my rv-b while merging it.
>
> Link: https://bugzilla.openanolis.cn/show_bug.cgi?id=3414
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
> ---
> Changes in v2:
> -Remove the comment block.
>
> drivers/gpu/drm/i915/gt/uc/intel_guc_hwconfig.c | 6 ------
> 1 file changed, 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc_hwconfig.c
> b/drivers/gpu/drm/i915/gt/uc/intel_guc_hwconfig.c
> index 4781fccc2687..5559d39881ee 100644
> --- a/drivers/gpu/drm/i915/gt/uc/intel_guc_hwconfig.c
> +++ b/drivers/gpu/drm/i915/gt/uc/intel_guc_hwconfig.c
> @@ -102,12 +102,6 @@ static bool has_table(struct drm_i915_private
> *i915)
> return false;
> }
>
> -/**
> - * intel_guc_hwconfig_init - Initialize the HWConfig
> - *
> - * Retrieve the HWConfig table from the GuC and save it locally.
> - * It can then be queried on demand by other users later on.
> - */
> static int guc_hwconfig_init(struct intel_gt *gt)
> {
> struct intel_hwconfig *hwconfig = >->info.hwconfig;
prev parent reply other threads:[~2022-12-13 13:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 5:50 [Intel-gfx] [PATCH v2] drm/i915/hwconfig: Remove comment block Jiapeng Chong
2022-12-13 7:16 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2022-12-13 13:33 ` Vivi, Rodrigo [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=3221542bbaf123525fa35a38bb1a4c5c1d0d292d.camel@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=abaci@linux.alibaba.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
/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