All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Peter Soetens <peter.soetens@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] Comedi drivers in Xenomai porting/integration status ?
Date: Thu, 19 Feb 2009 17:22:43 +0100	[thread overview]
Message-ID: <499D8753.8070109@domain.hid> (raw)
In-Reply-To: <200902191308.31266.peter.soetens@domain.hid>

Peter Soetens wrote:
> On Thursday 19 February 2009 00:43:56 Alexis Berlemont wrote:
>> Hi,
>>
>>>> That was the reason why, I was really suprised to find Comedi
>>>> integrated into the mainline kernel. What strikes me more is that
>>>> Comedi seems to be left as is. Do you think, it will be cleaned up or
>>>> reworked ?
>>> Without rework Comedi will not make into mainline (I wouldn't call the
>>> staging corner "mainline"). And when reading this
>>> http://permalink.gmane.org/gmane.linux.kernel/793476, it is probably the
>>> best time now to propose interface changes and contribute back
>>> improvements made for the RTDM rework.
>> How would you proceed ? Maybe, the first step would be to ask on the
>> Comedi mailing-list if someone is interested in discussing on the API
>> rework. Maybe, someone will answer this time.
> 
> Much wil depend on how you approach upstream. An example: Keith Packard and 
> Ingo Molnar managed to push major changes into the Linux kernel mainline. Not 
> by forcing yet another architecture into Linus' throat, but by saying "Hey, I 
> need these video services from the kernel, how should we fix that?" or saying: 
> 'Look how broken locking imlementation X is, I have a patch that cleans it up, 
> and by the way, adds priority inheritance." 
> 
> What I'm saying is tht it's very risky to ask upstream to move to you. But if 
> you move to upstream, success is almost guaranteed.

Another lesson to term: Step by step.

It might be a good idea to start the discussion with (probably) less
controversial proposals, proving that way that you are willing to
contribute and able to provide good changes, and after that starting
discussions on more invasive modifications.

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux


  reply	other threads:[~2009-02-19 16:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-16 12:55 [Xenomai-core] Comedi drivers in Xenomai porting/integration status ? Cristian Axenie
2009-02-16 23:00 ` Alexis Berlemont
2009-02-17  8:10   ` Cristian Axenie
2009-02-17  8:40   ` Peter Soetens
2009-02-17  9:41     ` Jan Kiszka
2009-02-17 11:08       ` Peter Soetens
2009-02-17 11:21         ` Jan Kiszka
2009-02-18  1:20         ` Alexis Berlemont
2009-02-18  7:38           ` Jan Kiszka
2009-02-18 23:43             ` Alexis Berlemont
2009-02-19  8:21               ` Anders Blomdell
2009-02-19 10:19               ` Jan Kiszka
2009-02-19 12:08               ` Peter Soetens
2009-02-19 16:22                 ` Jan Kiszka [this message]
2009-02-17  9:27   ` Jan Kiszka

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=499D8753.8070109@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=peter.soetens@domain.hid \
    --cc=xenomai@xenomai.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 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.