From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [WIP 1/7] drm: Decouple EDID parsing from I2C adapter
Date: Thu, 03 Apr 2014 00:12:39 +0000 [thread overview]
Message-ID: <2998648.mNRJR98WlL@avalon> (raw)
In-Reply-To: <1396439205-26199-2-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
Hi Geert,
Thank you for the review.
On Wednesday 02 April 2014 13:54:31 Geert Uytterhoeven wrote:
> On Wed, Apr 2, 2014 at 1:46 PM, Laurent Pinchart wrote:
> > From: Lars-Peter Clausen <lars@metafoo.de>
> >
> > --- a/drivers/gpu/drm/drm_edid.c
> > +++ b/drivers/gpu/drm/drm_edid.c
> > @@ -1106,9 +1106,10 @@ EXPORT_SYMBOL(drm_edid_is_valid);
> > * Try to fetch EDID information by calling i2c driver function.
> > */
> > static int
> > -drm_do_probe_ddc_edid(struct i2c_adapter *adapter, unsigned char *buf,
> > +drm_do_probe_ddc_edid(void *data, unsigned char *buf,
> > int block, int len)
>
> If you touch the signature, I suggest to also change the buffer pointer
> to "void *", and its size to "unsigned int".
I'd even go for size_t for the size. What about u8 * for the buffer, given
that it's really a buffer of bytes ?
> "block" should also be "unsigned int"?
Indeed.
> > --- a/include/drm/drm_edid.h
> > +++ b/include/drm/drm_edid.h
> > @@ -274,4 +274,8 @@ int
> > drm_hdmi_vendor_infoframe_from_display_mode(struct hdmi_vendor_infoframe
> > *frame,
> > const struct drm_display_mode
> > *mode);
> > +struct edid *drm_do_get_edid(struct drm_connector *connector,
> > + int (*get_edid_block)(void *, unsigned char *buf, int, int),
> > + void *data);
>
> Same here, this is new code, so better get the types right.
>
> > +
> > #endif /* __DRM_EDID_H__ */
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2014-04-03 0:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 11:46 [WIP 1/7] drm: Decouple EDID parsing from I2C adapter Laurent Pinchart
2014-04-02 11:54 ` Geert Uytterhoeven
2014-04-03 0:12 ` Laurent Pinchart [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=2998648.mNRJR98WlL@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-sh@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;
as well as URLs for NNTP newsgroup(s).