public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Petri Latvala <petri.latvala@intel.com>
To: Caz Yokoyama <Caz.Yokoyama@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH 1/1] lib: consolidate duplicated define of vfs_file_max(void)
Date: Wed, 24 Apr 2019 13:19:48 +0300	[thread overview]
Message-ID: <20190424101948.GX22949@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <d725813c4f54ba83b26393f8af47fef2b64bec7a.camel@intel.com>

On Wed, Apr 17, 2019 at 07:49:35AM -0700, Caz Yokoyama wrote:
> Petri,
> To where Documentation goes to? To commit message? To one of the files
> in docs directory? man directory?
> It may be obvious for you, but please clarify for clear understanding
> on both of us.
> Thank you.
> -caz

In the source, above the function definition, in gtk-doc format.

An example from elsewhere in intel_os.c:

/**
 * intel_get_avail_ram_mb:
 *
 * Returns:
 * The amount of unused system RAM available in MB.
 */
uint64_t
intel_get_avail_ram_mb(void)
{
 ....




-- 
Petri Latvala
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

      reply	other threads:[~2019-04-24 10:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-16 15:57 [igt-dev] [PATCH 1/1] lib: consolidate duplicated define of vfs_file_max(void) Caz Yokoyama
2019-04-16 17:33 ` [igt-dev] ✗ Fi.CI.BAT: failure for series starting with [1/1] " Patchwork
2019-04-17  8:12 ` [igt-dev] [PATCH 1/1] " Petri Latvala
2019-04-17 14:49   ` Caz Yokoyama
2019-04-24 10:19     ` Petri Latvala [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=20190424101948.GX22949@platvala-desk.ger.corp.intel.com \
    --to=petri.latvala@intel.com \
    --cc=Caz.Yokoyama@intel.com \
    --cc=igt-dev@lists.freedesktop.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