public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Greg KH <gregkh@suse.de>
Cc: "Othman, Ossama" <ossama.othman@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Randy Dunlap <randy.dunlap@oracle.com>
Subject: Re: [PATCH] Intel Restricted Access Region Handler
Date: Fri, 19 Mar 2010 14:32:22 -0700	[thread overview]
Message-ID: <20100319143222.72aee474.akpm@linux-foundation.org> (raw)
In-Reply-To: <20100315234508.GB4008@suse.de>

On Mon, 15 Mar 2010 16:45:08 -0700
Greg KH <gregkh@suse.de> wrote:

> On Mon, Mar 15, 2010 at 04:16:02PM -0700, Othman, Ossama wrote:
> > Greg, Randy,
> > 
> > > Can you also send me a patch, that adds a TODO file to the directory of
> > > this driver, that explains what you think needs to be done in order to
> > > get this code merged into the main portion of the kernel tree, and
> > > include your email address in it so that people who wish to send
> > > patches, know who to copy on them?
> > > 
> > > See the other drivers/staging/*/TODO files for an example of what is
> > > expected here.
> > 
> > I just resubmitted a consolidated patch that includes the TODO file
> > you requested, as well as the kernel-doc related updates that Randy
> > requested.  Randy, I know that you were not in a rush to get them.  I
> > just wanted to get them out of the way.
> 
> Looks good, I'll queue it up in a few days.

Then what happens?  I guess I still don't understand the -staging process.

Does the code get re-posted for re-review?  If so, who does this?  How
do we ensure that suitably experienced/motivated reviewers and testers
take a look at this code?

Or does it just fester in -staging until we get bored of it then it
gets merged anyway?

Regarding the code itself: it appears to implement a userspace
interface via some /dev node.  But there is no description of this
interface at all in the changelog and there is no documentation
provided.  But the userspace-facing interface is the most important
part of the entire feature, because it is something we cannot ever
change.  It should be exhaustively described right up-front in the
changelog so that reviewers can easily and fully understand the
proposed API.


  reply	other threads:[~2010-03-19 21:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-14  9:14 [PATCH] Intel Restricted Access Region Handler Ossama Othman
2010-03-14  9:08 ` Othman, Ossama
2010-03-14 18:10 ` Greg KH
2010-03-15 23:16   ` Othman, Ossama
2010-03-15 23:45     ` Greg KH
2010-03-19 21:32       ` Andrew Morton [this message]
2010-03-19 21:40         ` Greg KH
2010-03-19 22:53         ` Othman, Ossama
2010-03-19 22:56           ` Greg KH
2010-03-26 22:11             ` [PATCH] staging: Initial memrar ABI document Ossama Othman
2010-03-15 23:23   ` [PATCH] staging: Intel Restricted Access Region Handler Ossama Othman
2010-03-15 17:22 ` [PATCH] " Randy Dunlap
2010-03-15 17:26   ` Othman, Ossama
2010-03-15 17:47   ` Alan Cox
2010-03-15 18:29     ` Randy Dunlap

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=20100319143222.72aee474.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ossama.othman@intel.com \
    --cc=randy.dunlap@oracle.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