From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Chen Lin <chen45464546@163.com>
Cc: airlied@linux.ie, daniel@ffwll.ch,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, Chen Lin <chen.lin5@zte.com.cn>,
rodrigo.vivi@intel.com
Subject: Re: [PATCH] drm/i915: Remove unused function pointer typedef long_pulse_detect_func
Date: Tue, 16 Feb 2021 13:40:53 +0200 [thread overview]
Message-ID: <YCuvRTwGxocZULT1@intel.com> (raw)
In-Reply-To: <1613388619-3276-1-git-send-email-chen45464546@163.com>
On Mon, Feb 15, 2021 at 07:30:19PM +0800, Chen Lin wrote:
> From: Chen Lin <chen.lin5@zte.com.cn>
>
> Remove the 'long_pulse_detect_func' typedef as it is not used.
>
> Signed-off-by: Chen Lin <chen.lin5@zte.com.cn>
> ---
> drivers/gpu/drm/i915/i915_irq.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c
> index 6cdb052..c294ac6 100644
> --- a/drivers/gpu/drm/i915/i915_irq.c
> +++ b/drivers/gpu/drm/i915/i915_irq.c
> @@ -78,7 +78,6 @@ static inline void pmu_irq_stats(struct drm_i915_private *i915,
> WRITE_ONCE(i915->pmu.irq_count, i915->pmu.irq_count + 1);
> }
>
> -typedef bool (*long_pulse_detect_func)(enum hpd_pin pin, u32 val);
> typedef u32 (*hotplug_enables_func)(struct drm_i915_private *i915,
> enum hpd_pin pin);
I thought we used in when passing it as an argument to
intel_get_hpd_pins(), but looks like that's not the case.
I guess we should unify this stuff by either removing both
these typedefs and adjusting intel_hpd_hotplug_enables()
accordingly, or we should use the typedef in intel_get_hpd_pins() as
well.
--
Ville Syrjälä
Intel
next parent reply other threads:[~2021-02-16 11:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1613388619-3276-1-git-send-email-chen45464546@163.com>
2021-02-16 11:40 ` Ville Syrjälä [this message]
2021-02-16 15:39 ` [v2] drm/i915: Use function pointer typedef long_pulse_detect_func in intel_get_hpd_pins Chen Lin
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=YCuvRTwGxocZULT1@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=airlied@linux.ie \
--cc=chen.lin5@zte.com.cn \
--cc=chen45464546@163.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@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