From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] PXA: Fix typo in proc-xscale.S
Date: Thu, 28 Apr 2011 12:22:06 +0100 [thread overview]
Message-ID: <20110428112206.GF17290@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20110428104732.GO31131@pengutronix.de>
On Thu, Apr 28, 2011 at 12:47:32PM +0200, Uwe Kleine-K?nig wrote:
> another problem is that the patch system is for reviewed patches only.
> If the patch is forgotten before it gets some reply sending it to the
> patch system is wrong (at least for non-trivial patches).
That's where pester power comes in - if its still sitting around
unreviewed a week later (assuming there's no long holidays) then
it needs to be chased.
> Patchwork comes to mind. That doesn't forget patches.
> I think for that to be practical for lakml some automatic delegation
> would be needed though.
I'm not convinced that patchwork ultimately reduces the amount of work
required - I think it moves the workload from the patch submitter to
the folk reviewing patches and applying them, who are already overworked.
We have an army of patch submitters but relatively few people reviewing
and applying, so increasing their workload is not really fair. We need
the workload for people up the chain of patches (who handle a greater
volume of patches) to be less than those down the chain of patches.
Eg, I'm currently struggling to catch up with the email from the last
six days. Having spent about six hours over the last two days trying to
work through the backlog, I've made a fairly insignificant dent - about
1100 unread messages yesterday morning to 930 unread messages at around
this point in time. I estimate at this rate I'll have caught up by end
of next week - probably less because I normally seem to drop 10% of email
on the floor unanswered irrespective of the volume.
I already feel like I need another holiday!
prev parent reply other threads:[~2011-04-28 11:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-28 1:46 [PATCH] PXA: Fix typo in proc-xscale.S Marek Vasut
2011-04-28 6:48 ` Igor Grinberg
2011-04-28 9:25 ` Marek Vasut
2011-04-28 9:57 ` Eric Miao
2011-04-28 9:55 ` Russell King - ARM Linux
2011-04-28 10:35 ` Igor Grinberg
2011-04-28 10:47 ` Uwe Kleine-König
2011-04-28 11:22 ` Russell King - ARM Linux [this message]
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=20110428112206.GF17290@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).