From: Jonathan Cameron <jic23@cam.ac.uk>
To: Manuel Stahl <manuel.stahl@iis.fraunhofer.de>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"Hennerich, Michael" <Michael.Hennerich@analog.com>,
Amit Kucheria <amit.kucheria@verdurent.com>
Subject: Re: IIO: ownership of patches taking drivers out of staging.
Date: Tue, 27 Sep 2011 14:57:44 +0100 [thread overview]
Message-ID: <4E81D658.30801@cam.ac.uk> (raw)
In-Reply-To: <201109271534.09628.manuel.stahl@iis.fraunhofer.de>
On 09/27/11 14:34, Manuel Stahl wrote:
> Hi Jonathon,
>
> I'm fine with that. Of course we could also change ownership for adis16400 to
> Michael, as I don't have the time to actively support this one.
> I have a few others in the pipeline (lis331dlh, itg3200) that I will publish
> as soon as we have a stable API in mainline.
Cool. Unless Michael particularly wants it, why don't we put a maintainers
entry in that lists the Analog list along side linux-iio as contact points.
either Michael or I can then take the maintainer role as emails will get to
both of us (and you for that matter) anyway.
Jonathan
>
> Regards,
> Manuel
>
> Am Dienstag, 27. September 2011, 15:32:33 schrieb Jonathan Cameron:
>> Hi All,
>>
>> I'm putting together a patch set to propose the first step in moving
>> IIO out of the staging tree.
>>
>> I want to take a small set (initially) of representative drivers
>> along for the ride.
>>
>> Now unlike later elements which will consist of git moves (and hence
>> preserve history) those that come with us now will be done by
>> stripping down the drivers and then building their feature set
>> back up as we go.
>>
>> My question here is whether people are happy if I assign authorship
>> of patches for their drivers to them (with appropriate note and
>> sign off from me to explain where they came from).
>>
>> Right now my example set consists of
>>
>> ad799x - Michael's
>> max1363 - mine :)
>> tsl2583 - Amit's
>> adis16400 - Manuel's but with large bits from drivers of mine
>> and Barry Song. I'm fine with it being Manuel's.
>> Copyright notice covers that some of it is Analog's
>> so, Michael, is that fine with you guys?
>>
>> So I need responses from Amit, Michael and Manuel as to whether
>> they mind me setting author of relevant drivers to them? I'd
>> obviously also like sign offs once you have had time to look
>> at them. I'll post an updated tree shortly to github.
>>
>> Thanks,
>>
>> Jonathan
>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2011-09-27 13:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 13:32 IIO: ownership of patches taking drivers out of staging Jonathan Cameron
2011-09-27 13:34 ` Manuel Stahl
2011-09-27 13:57 ` Jonathan Cameron [this message]
2011-09-27 14:59 ` Amit Kucheria
2011-09-27 15:12 ` Jonathan Cameron
2011-09-28 6:58 ` Hennerich, Michael
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=4E81D658.30801@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=Michael.Hennerich@analog.com \
--cc=amit.kucheria@verdurent.com \
--cc=linux-iio@vger.kernel.org \
--cc=manuel.stahl@iis.fraunhofer.de \
/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).