| Message ID | 1432135622-8288-7-git-send-email-sudipm.mukherjee@gmail.com |
|---|---|
| State | Not Applicable |
| Headers | show |
On Wed, May 20, 2015 at 5:27 PM, Sudip Mukherjee <sudipm.mukherjee@gmail.com> wrote: > Lets give the parport subsystem a proper name and start > maintaining the files. Excuse me, but usually someone takes over the maintainer role after proving that he cares for a sub system for a certain period of time. Or did I miss something?
On Wed, 2015-05-20 at 17:46 +0200, Richard Weinberger wrote: > On Wed, May 20, 2015 at 5:27 PM, Sudip Mukherjee > <sudipm.mukherjee@gmail.com> wrote: > > Lets give the parport subsystem a proper name and start > > maintaining the files. > > Excuse me, but usually someone takes over the maintainer role after > proving that he > cares for a sub system for a certain period of time. > Or did I miss something? MAINTAINERS:85: Orphan: No current maintainer [but maybe you could take the MAINTAINERS-86- role as you write your new code]. Parport is an orphan, hasn't had a maintainer since at least 2.6.12, and has almost no activity minus drive-by cleanups and new device ID support every once in awhile. Sudip is writing new code. If Sudip wants to be a maintainer of parport, assuming he has the time and resources to give it a go, I think he should be welcomed to it. Thanks Sudip. Best of luck... -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wed, 20 May 2015 17:46:44 +0200 Richard Weinberger <richard.weinberger@gmail.com> wrote: > On Wed, May 20, 2015 at 5:27 PM, Sudip Mukherjee > <sudipm.mukherjee@gmail.com> wrote: > > Lets give the parport subsystem a proper name and start > > maintaining the files. > > Excuse me, but usually someone takes over the maintainer role after > proving that he > cares for a sub system for a certain period of time. > Or did I miss something? It currently (and for some time) has had no maintainer so having a maintainer is IMHO definitely an improvement in things. Alan -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wed, May 20, 2015 at 09:28:16AM -0700, Joe Perches wrote: > On Wed, 2015-05-20 at 17:46 +0200, Richard Weinberger wrote: > > On Wed, May 20, 2015 at 5:27 PM, Sudip Mukherjee > > <sudipm.mukherjee@gmail.com> wrote: > > > Lets give the parport subsystem a proper name and start > > > maintaining the files. > > > > Excuse me, but usually someone takes over the maintainer role after > > proving that he > > cares for a sub system for a certain period of time. > > Or did I miss something? > > MAINTAINERS:85: Orphan: No current maintainer [but maybe you could take the > MAINTAINERS-86- role as you write your new code]. > > Parport is an orphan, hasn't had a maintainer since at > least 2.6.12, and has almost no activity minus drive-by > cleanups and new device ID support every once in awhile. > > Sudip is writing new code. > > If Sudip wants to be a maintainer of parport, assuming > he has the time and resources to give it a go, I think > he should be welcomed to it. > > Thanks Sudip. Best of luck... Thanks Joe & Alan for the support. I consider myself inexperienced to maintain a subsystem, but I hope you all will be there to review and help me in the process. regards sudip -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Am 20.05.2015 um 18:33 schrieb One Thousand Gnomes: > On Wed, 20 May 2015 17:46:44 +0200 > Richard Weinberger <richard.weinberger@gmail.com> wrote: > >> On Wed, May 20, 2015 at 5:27 PM, Sudip Mukherjee >> <sudipm.mukherjee@gmail.com> wrote: >>> Lets give the parport subsystem a proper name and start >>> maintaining the files. >> >> Excuse me, but usually someone takes over the maintainer role after >> proving that he >> cares for a sub system for a certain period of time. >> Or did I miss something? > > It currently (and for some time) has had no maintainer so having a > maintainer is IMHO definitely an improvement in things. Having a maintainer is good. All I wanted to point out was that it is IMHO uncommon to claim maintainership before being the main contributor or the de facto maintainer of a subsystem. This "rule" prevents us from "Mommy!!! Look, I'm a maintainer!!!1" patches. ;-) Thanks, //richard -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wed, May 20, 2015 at 05:46:44PM +0200, Richard Weinberger wrote: > On Wed, May 20, 2015 at 5:27 PM, Sudip Mukherjee > <sudipm.mukherjee@gmail.com> wrote: > > Lets give the parport subsystem a proper name and start > > maintaining the files. > > Excuse me, but usually someone takes over the maintainer role after > proving that he > cares for a sub system for a certain period of time. > Or did I miss something? Sudip has been volunteering for fixing this code which is marked as "orphan". So whatever his experience and care in this area, it will be better for the driver to have a maintainer than none. Good luck Sudip, as drivers which have become orphans are probably the ones that deserve the least love :-) Willy -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wed, May 20, 2015 at 10:36:04PM +0200, Richard Weinberger wrote: > Am 20.05.2015 um 18:33 schrieb One Thousand Gnomes: > > On Wed, 20 May 2015 17:46:44 +0200 > > Richard Weinberger <richard.weinberger@gmail.com> wrote: > > > >> On Wed, May 20, 2015 at 5:27 PM, Sudip Mukherjee > >> <sudipm.mukherjee@gmail.com> wrote: > >>> Lets give the parport subsystem a proper name and start > >>> maintaining the files. > >> > >> Excuse me, but usually someone takes over the maintainer role after > >> proving that he > >> cares for a sub system for a certain period of time. > >> Or did I miss something? > > > > It currently (and for some time) has had no maintainer so having a > > maintainer is IMHO definitely an improvement in things. > > Having a maintainer is good. > All I wanted to point out was that it is IMHO uncommon to claim maintainership > before being the main contributor or the de facto maintainer of a > subsystem. > > This "rule" prevents us from "Mommy!!! Look, I'm a maintainer!!!1" patches. ;-) I already have my name in the MAINTAINERS file, so that is not a cookie to cry for. Personnaly I will prefer Joe Perches or Dan Carpenter to be the maintainer. They have reviewed many of my patches since I started contributing here and I have learnt and still learning many things from them. if this patch is a debatable topic, then lets drop it. I have written these changes, and will write the next changes also, it doesnot matter if my name is there in the MAINTAINERS or not. The main reason I gave this patch is just because if any problem (read as regression) arises due to these changes then those problem mails would have directly come to my inbox. regards sudip > > Thanks, > //richard -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, May 21, 2015 at 07:51:18AM +0200, Willy Tarreau wrote: > On Wed, May 20, 2015 at 05:46:44PM +0200, Richard Weinberger wrote: > > On Wed, May 20, 2015 at 5:27 PM, Sudip Mukherjee > > <sudipm.mukherjee@gmail.com> wrote: > > > Lets give the parport subsystem a proper name and start > > > maintaining the files. > > > > Excuse me, but usually someone takes over the maintainer role after > > proving that he > > cares for a sub system for a certain period of time. > > Or did I miss something? > > Sudip has been volunteering for fixing this code which is marked > as "orphan". So whatever his experience and care in this area, > it will be better for the driver to have a maintainer than none. > > Good luck Sudip, as drivers which have become orphans are probably > the ones that deserve the least love :-) I agree. I've been "baby-sitting" this subsystem for a long time now. If Sudip wants to take it on, and based on his recent patches it looks like he does, I'm all for him to be the maintainer of it. So this patch in the series is fine with me, I'll apply it when the rest of this series gets merged. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/MAINTAINERS b/MAINTAINERS index 86d9398..0eb5ce2 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -7476,13 +7476,16 @@ S: Maintained F: Documentation/mn10300/ F: arch/mn10300/ -PARALLEL PORT SUPPORT +PARALLEL PORT SUBSYSTEM +M: Sudip Mukherjee <sudipm.mukherjee@gmail.com> +M: Sudip Mukherjee <sudip@vectorindia.org> L: linux-parport@lists.infradead.org (subscribers-only) -S: Orphan +S: Maintained F: drivers/parport/ F: include/linux/parport*.h F: drivers/char/ppdev.c F: include/uapi/linux/ppdev.h +F: Documentation/parport*.txt PARAVIRT_OPS INTERFACE M: Jeremy Fitzhardinge <jeremy@goop.org>
Lets give the parport subsystem a proper name and start maintaining the files. Signed-off-by: Sudip Mukherjee <sudip@vectorindia.org> --- MAINTAINERS | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-)