IIO: ownership of patches taking drivers out of staging.
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
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.
Regards,
Manuel
Am Dienstag, 27. September 2011, 15:32:33 schrieb Jonathan Cameron:
Quoted 41 lines
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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 6 lines · Manuel Stahl
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
Quoted 47 lines
Regards,
ManuelAm Dienstag, 27. September 2011, 15:32:33 schrieb Jonathan Cameron:
Quoted 41 lines
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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 27 lines · 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?
Quoted 5 lines
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.
Yes, that'd be fine. I'll try to test out the changes/moves as we go but I won't be close to HW and a reliable internet connection over the next few weeks.
/Amit
Quoted 34 lines · Amit Kucheria
Quoted 27 lines · 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?Quoted 5 lines
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.
Quoted 6 lines
Yes, that'd be fine. I'll try to test out the changes/moves as we go but I won't be close to HW and a reliable internet connection over the next few weeks.
/Amit
Not to worry. It's a rare thing but I actually have a part to test that particular driver (have a tsl2561)
Thanks,
Jonathan
RE: ownership of patches taking drivers out of staging.
In reply to Jonathan CameronJonathan Cameron wrote on 2011-09-27:
Quoted 27 lines
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?
Quoted 2 lines
So I need responses from Amit, Michael and Manuel as to whether they mind me setting author of relevant drivers to them?
Hi Jonathan,
Sure - no problem.
Quoted 9 lines
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
Greetings,
Michael
--
Analog Devices GmbH Wilhelm-Wagenfeld-Str. 6 80807 Muenchen
Sitz der Gesellschaft: Muenchen; Registergericht: Muenchen HRB 40368; Geschaeftsfuehrer:Dr.Carsten Suckrow, Thomas Wessel, William A. Martin, Mar= garet Seif