From: Kalle Valo <kvalo@codeaurora.org>
To: linux-wireless@vger.kernel.org
Subject: wireless-drivers: random cleanup patches piling up
Date: Thu, 21 Jan 2016 16:58:44 +0200 [thread overview]
Message-ID: <87wpr3x9ln.fsf@kamboji.qca.qualcomm.com> (raw)
Hi,
I have quite a lot of random cleanup patches from new developers waiting
in my queue:
https://patchwork.kernel.org/project/linux-wireless/list/?state=10&delegate=25621&order=date
(Not all of them are cleanup patches, there are also few patches
deferred due to other reasons, but you get the idea.)
These cleanup patches usually take quite a lot of my time and I'm
starting to doubt the benefit, compared to the time needed to dig
through them and figuring out what to apply. And this is of course time
away from other patches, so it's slowing down "real" development.
I really don't know what to do. Part of me is saying that I just should
drop them unless it's reviewed by a more experienced developer but on
the other hand this is a good way get new developers onboard.
What others think? Are these kind of patches useful?
--
Kalle Valo
next reply other threads:[~2016-01-21 14:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 14:58 Kalle Valo [this message]
2016-01-21 19:46 ` wireless-drivers: random cleanup patches piling up Larry Finger
2016-01-22 12:11 ` Kalle Valo
2016-01-21 22:32 ` Julian Calaby
2016-01-22 12:17 ` Kalle Valo
2016-01-22 13:13 ` Julian Calaby
2016-01-22 0:52 ` Joe Perches
2016-01-22 7:30 ` Dan Carpenter
2016-01-22 12:21 ` Kalle Valo
2016-01-22 15:12 ` John W. Linville
2016-01-22 15:54 ` Kalle Valo
2016-01-26 5:28 ` Sudip Mukherjee
2016-01-29 8:08 ` Kalle Valo
2016-02-01 4:41 ` Sudip Mukherjee
2016-02-01 8:21 ` Kalle Valo
2016-03-16 0:57 ` Julian Calaby
2016-03-16 9:22 ` Kalle Valo
2016-03-16 9:42 ` Julian Calaby
2016-03-18 1:06 ` Julian Calaby
2016-01-22 18:05 ` Joe Perches
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wpr3x9ln.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).