All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jesse.barnes@intel.com>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org, mingo@elte.hu,
	dwalker@mvista.com
Subject: Re: [PATCH] maximum latency tracking infrastructure (version 3)
Date: Mon, 28 Aug 2006 09:30:45 -0700	[thread overview]
Message-ID: <200608280930.45273.jesse.barnes@intel.com> (raw)
In-Reply-To: <44F318F8.3050100@linux.intel.com>

On Monday, August 28, 2006 9:25 am, Arjan van de Ven wrote:
> Jesse Barnes wrote:
> > On Monday, August 28, 2006 8:48 am, Arjan van de Ven wrote:
> >> 3rd version; only minor changes this time, the sysreq stuff is gone
> >> however.
> >>
> >> I've decided to not use a namespace prefix; these functions are
> >> meant to be generic,  and a namespace prefix is not common for such
> >> functions, and it would in addition cause a too narrow usage of
> >> this infrastructure.
> >
> > Almost forgot--what about documentation?  This is an addition to the
> > driver API, so it should probably be described clearly somewhere,
> > probably in Documentation/ somewhere...
>
> how about linuxdoc??

I like to have stuff in Documentation/ too, but if you think the existing 
function comments are good enough that's fine.

Jesse

      reply	other threads:[~2006-08-28 16:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-28 15:48 [PATCH] maximum latency tracking infrastructure (version 3) Arjan van de Ven
2006-08-28 16:11 ` Andreas Mohr
2006-08-28 16:19   ` Arjan van de Ven
2006-08-28 16:27     ` Andi Kleen
2006-08-28 16:35     ` Andreas Mohr
2006-08-28 16:48       ` Arjan van de Ven
2006-08-28 16:25 ` Jesse Barnes
2006-08-28 16:25   ` Arjan van de Ven
2006-08-28 16:30     ` Jesse Barnes [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=200608280930.45273.jesse.barnes@intel.com \
    --to=jesse.barnes@intel.com \
    --cc=akpm@osdl.org \
    --cc=arjan@linux.intel.com \
    --cc=dwalker@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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.