develoment workflow: how to avoid duplicate work ?

[Hugo Lefeuvre]

Hi,

I've started to take a look at TODO entries in the staging drivers
subtree and found some issues in pi433 I'd like to work on. Before
starting to prepare my patch, I tried to check the LKML and the bug
tracker to make sure nobody was working on the same issues as me
(this driver seems to be pretty actively developed), but couldn't
find anything helpful. No mailing list, nobody coordinating, only
single patches without relationship.

Did I miss something ? Is there a specific place where I can coordinate
with the rest of the kernel dev community and make people aware I'm
working on this particular issue ? (apart from the bug tracker, which
doesn't seem to be very active when it comes to the staging subtree)

Thanks !

Regards,
 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/20180528/90908f68/attachment.sig>