develoment workflow: how to avoid duplicate work ?

[Hugo Lefeuvre]

Hi Greg,

> No need to coordinate anything, just start sending patches against the
> latest development tree (linux-next, or the staging.git staging-next
> branch), and all will be fine.
> 
> If there are conflicts, the maintainer will let you know, but they are
> usually quite rare.

Then I will simply submit my patch and let the maintainer check for
conflicts.

Thanks for your answer.

Cheers,
 Hugo

-- 
             Hugo Lefeuvre (hle)    |    www.owl.eu.com
4096/ 9C4F C8BF A4B0 8FC5 48EB 56B8 1962 765B B9A8 BACA
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20180529/44982563/attachment.sig>