From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: maranello for staging ?
Date: Thu, 24 Mar 2011 13:50:02 -0700 [thread overview]
Message-ID: <20110324205002.GA15293@kroah.com> (raw)
In-Reply-To: <AANLkTimLn4Rm5aMTtPGjbNoPA5KR8sG80-mGwb2tUaSW@mail.gmail.com>
On Thu, Mar 24, 2011 at 02:19:43PM -0600, Jim Cromie wrote:
> Im not quite sure how to proceed with this, Ive refrained from
> sending to netdev at kernel.org, I guess Id like advice and feedback 1st.
First get feedback from them, if the protocol isn't going to be accepted
as-is from them, or with just minor work, then we can take it in the
staging tree, but you must list what is needed to be done to get it into
mergable state.
As for your other questions:
- yes, we want original authorship.
- we need patches, not a git tree, to apply to the kernel, so however
you feel that getting the patches into a state that I can apply them
is fine to do. Just note that you can't send out "merged into..."
patches as they make no sense :)
thanks,
greg k-h
prev parent reply other threads:[~2011-03-24 20:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 20:19 maranello for staging ? Jim Cromie
2011-03-24 20:50 ` Greg KH [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=20110324205002.GA15293@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).