From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Kurachkin Michail <Michail.Kurachkin@promwad.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Kuten Ivan <Ivan.Kuten@promwad.com>,
Josh Triplett <josh@joshtriplett.org>
Subject: Re: TDM bus support in Linux Kernel
Date: Wed, 28 Nov 2012 15:38:45 -0800 [thread overview]
Message-ID: <20121128233845.GA16396@kroah.com> (raw)
In-Reply-To: <F7F628C32E67B04DAECC5CA53521253E5F9D9350@sv-exmb01-lo1.promwad.corp>
On Mon, Nov 19, 2012 at 11:00:12AM +0000, Kurachkin Michail wrote:
> Hi Greg,
>
> During the work on developing VoIP network router I designed TDM bus subsystem and wrote SLIC driver for si3226x. This code was developed for the commercial project, and now I am willing to release it under GPL.
> Please review my sources (or give me a clue on what to do next) and give some feedback on my work.
> https://github.com/stelhs/slic_tdm.git
It's really hard to review a random git tree somewhere, and having it in
this form doesn't make it easy to add to the kernel tree itself.
So, could you take your git tree and convert it to a patch (or patches)
to be applied to the kernel.org tree and send it in email so we can see
what it looks like that way?
I'd recommend putting everything under drivers/staging/ for now, to make
it easier to accept at the moment, and it makes it easier to clean up
and fix up any issues in-kernel, instead of having to keep huge patches
outside of the tree.
Take a look at the file, Documentation/SubmittingPatches for how to
create a patch and what I need in order for it to be able to be applied.
thanks,
greg k-h
prev parent reply other threads:[~2012-11-28 23:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 8:59 TDM bus support in Linux Kernel Viktar Palstsiuk
2012-02-03 11:00 ` Josh Triplett
2012-11-19 11:00 ` Kurachkin Michail
2012-11-28 23:38 ` Greg Kroah-Hartman [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=20121128233845.GA16396@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Ivan.Kuten@promwad.com \
--cc=Michail.Kurachkin@promwad.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.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