> > about the change to start discussion. > > > Perhaps add a bit of text here about integrating patches send to you, > as maintainer of the driver, by random people. it's not integrating. It's reviewing and passing on for merge ;) fundamental difference. You don't "own" the driver in the tree. You just keep it nice and shiny and clean. Best done by blessing patches, and by developing in "patches" not "new codebase". The entire "new codebase" thinking is the problem with CVS-think. Think in patches (once merged), not in code/tree. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [Updated]: How to become a kernel driver maintainer
- From: "Jesper Juhl" <[email protected]>
- Re: [Updated]: How to become a kernel driver maintainer
- References:
- [PATCH]: How to be a kernel driver maintainer
- From: Ben Collins <[email protected]>
- [PATCH updated]: How to be a kernel driver maintainer
- From: Ben Collins <[email protected]>
- Re: [PATCH updated]: How to be a kernel driver maintainer
- From: Arjan van de Ven <[email protected]>
- Re: [PATCH updated]: How to be a kernel driver maintainer
- From: Ben Collins <[email protected]>
- Re: [PATCH updated]: How to be a kernel driver maintainer
- From: Arjan van de Ven <[email protected]>
- [Updated]: How to become a kernel driver maintainer
- From: Ben Collins <[email protected]>
- Re: [Updated]: How to become a kernel driver maintainer
- From: "Jesper Juhl" <[email protected]>
- [PATCH]: How to be a kernel driver maintainer
- Prev by Date: Re: [PATCH] Document Linux's memory barriers [try #2]
- Next by Date: Re: [Updated]: How to become a kernel driver maintainer
- Previous by thread: Re: [Updated]: How to become a kernel driver maintainer
- Next by thread: Re: [Updated]: How to become a kernel driver maintainer
- Index(es):
 |