From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM: 7653/2: do not scale loops_per_jiffy when using a constant delay clock
Date: Wed, 6 Mar 2013 18:37:51 +0000 [thread overview]
Message-ID: <20130306183751.GV17833@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20130306022308.GA21539@mudshark.cambridge.arm.com>
On Wed, Mar 06, 2013 at 02:23:08AM +0000, Will Deacon wrote:
> I notice that commit 70264367a243 ("ARM: 7653/2: do not scale loops_per_jiffy
> when using a constant delay clock") is in mainline, but I'm not sure whether
> it's the right fix. Unfortunately, I failed to find it in the list archives,
> so I couldn't repy to the original patch.
Sigh. Here we go again. I've said this many times. Patches need to be
sent to the mailing list *before* they're sent to the patch system. Not
just the complex ones. ALL PATCHES including those which look like simple
fixes.
The reason being is that if someone wants to comment on the patch, they
can. For exactly the kind of reason that Will brings up above. You may
think your fix is obvious and the right solution, but someone else in this
complex ecosystem may have a case where your otherwise perfect solution
doesn't work.
next prev parent reply other threads:[~2013-03-06 18:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 2:23 ARM: 7653/2: do not scale loops_per_jiffy when using a constant delay clock Will Deacon
2013-03-06 18:37 ` Russell King - ARM Linux [this message]
2013-03-07 3:32 ` Will Deacon
2013-03-07 6:37 ` Nicolas Pitre
2013-03-19 18:16 ` Will Deacon
2013-03-19 19:00 ` Nicolas Pitre
2013-03-07 9:22 ` Russell King - ARM Linux
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=20130306183751.GV17833@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).