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: Thu, 7 Mar 2013 09:22:58 +0000 [thread overview]
Message-ID: <20130307092258.GB17833@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20130307033221.GC25137@mudshark.cambridge.arm.com>
On Thu, Mar 07, 2013 at 03:32:21AM +0000, Will Deacon wrote:
> Of course, this still isn't the right way to get patches into mainline and
> the points Russell makes above are completely correct. I wonder if we could
> extend the patch system to reject patches automatically if they don't appear
> in the linux-arm-kernel archives?
Ah, so what you're saying is that people can't be trusted to behave in a
responsible and professional manner. :)
How can that be done? Parse the patch escaping all the special characters
as appropriate, passing it across to the ARM920T based list server, and
having that take a while to grep 600MB of linux-arm-kernel archive -
and have it fail because it got turned into quoted-printable or base64
encoded because of the UTF-8 used in the email message?
What you suggest sounds simple, but in practise it is a very hairy problem.
prev parent reply other threads:[~2013-03-07 9:22 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
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 [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=20130307092258.GB17833@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).