public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Akira Hayakawa <ruby.wktk@gmail.com>
Cc: dm-devel@redhat.com, kernelnewbies@kernelnewbies.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC] dm-lc: plan to go to staging
Date: Wed, 28 Aug 2013 19:05:55 -0700	[thread overview]
Message-ID: <20130829020555.GA26206@kroah.com> (raw)
In-Reply-To: <521EA567.1070801@gmail.com>

On Thu, Aug 29, 2013 at 10:35:35AM +0900, Akira Hayakawa wrote:
> Hi,
> 
> I am happy to see that dm-lc is picked up by LWN.
> http://lwn.net/Articles/562938/
> 
> Now I think I should consider the next step forward.
> 
> 
> As Joe Thornber said before, what I have to do next are
> 1. Get some feedback from 3rd party users.
> 2. Reviewed by Mike Snitzer.
> As in
> http://www.redhat.com/archives/dm-devel/2013-July/msg00137.html
> 
> To achieve the first goal,
> I am thinking of going to staging tree
> for dm-lc to be widely available to people in community.
> 
> dm-lc is now managed in Github repo as a kernel module
> however, getting available in the tree means a lot
> to get 3rd party users.
> 
> Does this plan sound nice?
> 
> If so, what is the next step to go to staging?
> I have a patch against 3.11-rc7 in linux-next locally.
> Sending the patch to Greg is the next step?
> And who and what should be included in CC?

That's fine with me.  For staging drivers, I need a TODO file that lists
what needs to be done to the code to get it into a mergable state for
the "real" part of the kernel, and an email address to cc: patches on.
Also, a MAINTAINERS entry is good as that way the
scripts/get_maintainer.pl tool will properly pick up your email address.

You should generate the patch against the linux-next tree, as I have
lots of new staging drivers in there, ready for 3.12, and if you make a
patch against 3.11-rc7, odds are it will not apply properly.

If you have any other questions, please let me know.

thanks,

greg k-h

  reply	other threads:[~2013-08-29  2:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-29  1:35 [RFC] dm-lc: plan to go to staging Akira Hayakawa
2013-08-29  2:05 ` Greg KH [this message]
2013-08-29  3:30   ` [dm-devel] " Alasdair G Kergon
2013-08-29 14:45     ` Mikulas Patocka
2013-08-30 12:33       ` Akira Hayakawa
2013-08-30 12:50         ` Alasdair G Kergon
2013-08-30 14:41           ` Akira Hayakawa
2013-08-30 14:47         ` Valdis.Kletnieks
2013-08-31 14:25           ` [dm-devel] [RFC] dm-writeboost: " Akira Hayakawa
2013-08-31 14:32     ` Akira Hayakawa

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=20130829020555.GA26206@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dm-devel@redhat.com \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ruby.wktk@gmail.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