From mboxrd@z Thu Jan  1 00:00:00 1970
From: greg@kroah.com (Greg KH)
Date: Tue, 29 May 2018 07:50:12 +0200
Subject: develoment workflow: how to avoid duplicate work ?
In-Reply-To: <20180529030706.GD1845@hle-laptop.local>
References: <20180529030706.GD1845@hle-laptop.local>
Message-ID: <20180529055012.GA30116@kroah.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

On Mon, May 28, 2018 at 11:07:06PM -0400, Hugo Lefeuvre wrote:
> 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)

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.

good luck!

greg k-h