linux-modules.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Grover <agrover@redhat.com>
To: Lucas De Marchi <lucas.de.marchi@gmail.com>
Cc: Lucas De Marchi <lucas.demarchi@profusion.mobi>,
	linux-modules <linux-modules@vger.kernel.org>,
	wking@tremily.us
Subject: Re: [announce] python-kmod 0.9
Date: Wed, 18 Dec 2013 17:20:25 -0800	[thread overview]
Message-ID: <52B249D9.9020805@redhat.com> (raw)
In-Reply-To: <CAKi4VALDxMP9YmomHhi5CPaTxG1cjdX1Ab+XoNE4=v=4p_HFaw@mail.gmail.com>

On 12/18/2013 11:38 AM, Lucas De Marchi wrote:
>>> Hey. I think I replied once that this could be better left off in its
>>> own repository. However I'm reconsidering this now... if you are still
>>> interested in merging into kmod, I think it would be good.
>>
>>
>> You bet. I'll start work on a patch.
>
> Ping.

Hi Lucas,

Sorry for the delay. Here's what I have so far:

https://github.com/agrover/kmod.git

Copied source in, modified configure.ac. But I'm pretty weak on 
automake. Basically the Python bindings need "python setup.py build" and 
"python setup.py install" for the relevant make targets, but that still 
needs to be hooked up :-/

Would you or some other kind soul that knows automake be willing to 
advise, or even fix this up the rest of the way?

Thanks -- Regards -- Andy

  reply	other threads:[~2013-12-19  1:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <509C4944.3040907@redhat.com>
2013-11-11 19:28 ` [announce] python-kmod 0.9 Lucas De Marchi
2013-11-11 19:40   ` Andy Grover
2013-12-18 19:38     ` Lucas De Marchi
2013-12-19  1:20       ` Andy Grover [this message]
2013-12-22 21:52         ` Lucas De Marchi
2014-03-24 12:02           ` Lucas De Marchi
2014-03-24 17:12             ` Andy Grover
2014-03-26 17:45               ` Lucas De Marchi
2014-03-26 20:32                 ` Andy Grover
2014-03-26 20:49                   ` Lucas De Marchi
2014-03-26 20:56                     ` Andy Grover

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=52B249D9.9020805@redhat.com \
    --to=agrover@redhat.com \
    --cc=linux-modules@vger.kernel.org \
    --cc=lucas.de.marchi@gmail.com \
    --cc=lucas.demarchi@profusion.mobi \
    --cc=wking@tremily.us \
    /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).