dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Nishanth Menon <nm@ti.com>
Cc: Dave Airlie <airlied@redhat.com>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH] drm/edid: kernel-doc minimal cleanup
Date: Fri, 1 Mar 2013 15:47:53 +0200	[thread overview]
Message-ID: <20130301134753.GC4469@intel.com> (raw)
In-Reply-To: <20130301134523.GA20420@kahuna>

On Fri, Mar 01, 2013 at 07:45:24AM -0600, Nishanth Menon wrote:
> On 14:43-20130301, Ville Syrjälä wrote:
> > On Thu, Feb 28, 2013 at 05:13:09PM -0600, Nishanth Menon wrote:
> [..]
> > > @@ -982,14 +982,14 @@ EXPORT_SYMBOL(drm_edid_is_valid);
> > >  
> > >  #define DDC_SEGMENT_ADDR 0x30
> > >  /**
> > > - * Get EDID information via I2C.
> > > - *
> > > - * \param adapter : i2c device adaptor
> > > - * \param buf     : EDID data buffer to be filled
> > > - * \param len     : EDID data buffer length
> > > - * \return 0 on success or -1 on failure.
> > > + * drm_do_probe_ddc_edid() - Get EDID information via I2C.
> > > + * @adapter:	i2c device adaptor
> > 
> > nit: adapter vs. adaptor
> Thanks for catching it.
> > 
> > > + * @buf:	EDID data buffer to be filled
> > > + * @block:	EDID block to get
> > > + * @len:	EDID data buffer length
> > >   *
> > >   * Try to fetch EDID information by calling i2c driver function.
> > > + * Return 0 on success or -1 on failure.
> > >   */
> > >  static int
> > >  drm_do_probe_ddc_edid(struct i2c_adapter *adapter, unsigned char *buf,
> > > @@ -1128,10 +1128,10 @@ out:
> > >  }
> > >  
> > >  /**
> > > - * Probe DDC presence.
> > > + * drm_probe_ddc() - Probe DDC presence
> > > + * @adapter:	i2c device adaptor
> > >   *
> > > - * \param adapter : i2c device adaptor
> > > - * \return 1 on success
> > > + * returns 1 on success
> > >   */
> > >  bool
> > >  drm_probe_ddc(struct i2c_adapter *adapter)
> > > @@ -1455,8 +1455,10 @@ bad_std_timing(u8 a, u8 b)
> > >  
> > >  /**
> > >   * drm_mode_std - convert standard mode info (width, height, refresh) into mode
> > > + * @connector: connector corresponding to the HDMI/DP sink
> > 
> > EDID isn't limited to HDMI/DP.
> > 
> [..]
> > >  
> > >  /**
> > >   * drm_rgb_quant_range_selectable - is RGB quantization range selectable?
> > > + * @edid: EDID data
> > 
> > nit: Different description for the same thing between this and the previous
> > hunk.
> agreed. How about just EDID data?

Fine by me.

-- 
Ville Syrjälä
Intel OTC

      reply	other threads:[~2013-03-01 13:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-28 23:13 [PATCH] drm/edid: kernel-doc minimal cleanup Nishanth Menon
2013-03-01 12:43 ` Ville Syrjälä
2013-03-01 13:45   ` Nishanth Menon
2013-03-01 13:47     ` Ville Syrjälä [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=20130301134753.GC4469@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=airlied@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=nm@ti.com \
    --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