All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Brahmajit <brahmajit.xyz@gmail.com>
Cc: linux-newbie <linux-newbie@vger.kernel.org>
Subject: Re: Build failure with GCC 15 in drivers/gpu/drm/display/drm_dp_dual_mode_helper.c
Date: Tue, 1 Oct 2024 17:10:47 +0300	[thread overview]
Message-ID: <ZvwC50KKrLPxAvN6@intel.com> (raw)
In-Reply-To: <ZvwA5_H6lVvL1eoc@intel.com>

On Tue, Oct 01, 2024 at 05:02:15PM +0300, Ville Syrjälä wrote:
> On Tue, Oct 01, 2024 at 07:18:23PM +0530, Brahmajit wrote:
> > On 01.10.2024 16:28, Ville Syrjälä wrote:
> > > Looks like gcc is warning about perfectly legal code
> > > (as far as the C standard goes).
> > > 
> > > But we could work around by adding room for the '\0' and
> > > s/sizeof(...)/DP_DUAL_MODE_HDMI_ID_LEN/ in the memcmp().
> > 
> > Sorry I'm new, but can we do something like this?
> > 
> > --- a/drivers/gpu/drm/display/drm_dp_dual_mode_helper.c
> > +++ b/drivers/gpu/drm/display/drm_dp_dual_mode_helper.c
> > @@ -158,13 +158,13 @@ ssize_t drm_dp_dual_mode_write(struct i2c_adapter *adapter,
> >  }
> >  EXPORT_SYMBOL(drm_dp_dual_mode_write);
> >  
> > -static bool is_hdmi_adaptor(const char hdmi_id[DP_DUAL_MODE_HDMI_ID_LEN])
> > +static bool is_hdmi_adaptor(const char hdmi_id[DP_DUAL_MODE_HDMI_ID_LEN+1])
> 
> This should not have the +1
> 
> >  {
> > -	static const char dp_dual_mode_hdmi_id[DP_DUAL_MODE_HDMI_ID_LEN] =

Also we shuld probably remind why the +1 is there.
So a comment here would be good. 

Eg.
/* +1 to avoid spurious -W<whatever> warnings */

> > +	static const char dp_dual_mode_hdmi_id[DP_DUAL_MODE_HDMI_ID_LEN+1] =
> >  		"DP-HDMI ADAPTOR\x04";
> >  
> >  	return memcmp(hdmi_id, dp_dual_mode_hdmi_id,
> > -		      sizeof(dp_dual_mode_hdmi_id)) == 0;
> > +		      DP_DUAL_MODE_HDMI_ID_LEN+1) == 0;
> 
> and neither should this
> 
> >  }
> >  
> >  static bool is_type1_adaptor(uint8_t adaptor_id)
> > 
> > -- 
> > Regards,
> > Brahmajit
> 
> -- 
> Ville Syrjälä
> Intel

-- 
Ville Syrjälä
Intel

  parent reply	other threads:[~2024-10-01 14:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-01  6:15 Build failure with GCC 15 in drivers/gpu/drm/display/drm_dp_dual_mode_helper.c Brahmajit
2024-10-01  6:18 ` Brahmajit
2024-10-01 13:28   ` Ville Syrjälä
2024-10-01 13:42     ` Brahmajit
2024-10-01 13:48     ` Brahmajit
2024-10-01 14:02       ` Ville Syrjälä
2024-10-01 14:06         ` Brahmajit
2024-10-01 14:12           ` Ville Syrjälä
2024-10-01 14:14             ` Brahmajit
2024-10-01 14:34               ` Brahmajit
2024-10-01 14:36               ` [PATCH 1/1] drm/display: Fix building with GCC 15 Brahmajit Das
2024-10-01 14:10         ` Ville Syrjälä [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-01 12:53 Build failure with GCC 15 in drivers/gpu/drm/display/drm_dp_dual_mode_helper.c Brahmajit

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=ZvwC50KKrLPxAvN6@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=brahmajit.xyz@gmail.com \
    --cc=linux-newbie@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 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.