Re: [PATCH updated]: How to be a kernel driver maintainer

[Grant Coady <gcoady@gmail.com>]

On Mon, 09 Jan 2006 08:34:09 -0500, Ben Collins <ben.collins@ubuntu.com> wrote:

>
>But it says "your primary code". I'm not sure of another way to put it.
>Obviously, they have to do their work, and their development on
>something that isn't in Linus tree. If they are doing this work, they
>need to make sure that when they diff for patches, that they merge
>changes before diffing. The only way this is close to automatic is with
>git. Any other method requires manually merging.
>
>How else would you explain this without telling them that git is
>required?

I have my name on one driver ;)  Once the driver is in the kernel 
I no longer need worry about the source nor backups of my driver, 
okay?  The primary code is in mainstream, this is how it works for 
'leaf node' driver maintainers, at least from my limited perspective.

During development I had to rediff against -mm_latest, as that is 
how drivers (usually?) start the path to mainstream.  But the only 
part need merging for a new driver is the Kconfig entry, a trivial 
issue?

Cheers,
Grant.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/