All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: konrad.wilk@oracle.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, bob.liu@oracle.com,
	devel@linuxdriverproject.org, liwanp@linux.vnet.ibm.com
Subject: Re: [PATCH] staging: ramster: add how-to document
Date: Mon, 20 May 2013 08:16:59 -0700	[thread overview]
Message-ID: <20130520151659.GA22709@kroah.com> (raw)
In-Reply-To: <93d217c4-1477-4cf6-9f38-d036e2fb0e08@default>

On Mon, May 20, 2013 at 07:55:35AM -0700, Dan Magenheimer wrote:
> Hey Greg --
> 
> Since this is documentation only and documents existing
> behavior, I'm not clear whether it is acceptable for
> an rcN release in the current cycle or must wait until
> the next window.  Since it is a new file, it should
> apply to either so I'll leave the choice up to you.

I'll add it now, it's "only" documentation :)

thanks,

greg k-h

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: konrad.wilk@oracle.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, bob.liu@oracle.com,
	devel@linuxdriverproject.org, liwanp@linux.vnet.ibm.com
Subject: Re: [PATCH] staging: ramster: add how-to document
Date: Mon, 20 May 2013 08:16:59 -0700	[thread overview]
Message-ID: <20130520151659.GA22709@kroah.com> (raw)
In-Reply-To: <93d217c4-1477-4cf6-9f38-d036e2fb0e08@default>

On Mon, May 20, 2013 at 07:55:35AM -0700, Dan Magenheimer wrote:
> Hey Greg --
> 
> Since this is documentation only and documents existing
> behavior, I'm not clear whether it is acceptable for
> an rcN release in the current cycle or must wait until
> the next window.  Since it is a new file, it should
> apply to either so I'll leave the choice up to you.

I'll add it now, it's "only" documentation :)

thanks,

greg k-h

  reply	other threads:[~2013-05-20 15:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<1369061537-20205-1-git-send-email-dan.magenheimer@oracle.com>
2013-05-20 14:55 ` [PATCH] staging: ramster: add how-to document Dan Magenheimer
2013-05-20 14:55   ` Dan Magenheimer
2013-05-20 15:16   ` Greg Kroah-Hartman [this message]
2013-05-20 15:16     ` Greg Kroah-Hartman
2013-05-20 14:52 Dan Magenheimer
2013-05-20 14:52 ` Dan Magenheimer

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=20130520151659.GA22709@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bob.liu@oracle.com \
    --cc=dan.magenheimer@oracle.com \
    --cc=devel@linuxdriverproject.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=liwanp@linux.vnet.ibm.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 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.