From: jamie@jamieiles.com (Jamie Iles)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: perf: use raw_spinlock_t for pmu_lock
Date: Wed, 1 Dec 2010 17:23:18 +0000 [thread overview]
Message-ID: <20101201172318.GG2898@pulham.picochip.com> (raw)
In-Reply-To: <004e01cb9177$2760c460$76224d20$@deacon@arm.com>
On Wed, Dec 01, 2010 at 04:45:25PM -0000, Will Deacon wrote:
> Hmm, I just use an smtp server for sending messages so the message *should*
> be ok. It's the receiving side of things where I get into trouble. If I look
> at the .patch I gave to git send-email with hexdump it has:
>
> 000007d0 69 74 65 28 76 61 6c 29 3b 0a 2d 09 73 70 69 6e |ite(val);.-.spin|
> 000007e0 5f 75 6e 6c 6f 63 6b 5f 69 72 71 72 65 73 74 6f |_unlock_irqresto|
> 000007f0 72 65 28 26 70 6d 75 5f 6c 6f 63 6b 2c 20 66 6c |re(&pmu_lock, fl|
> 00000800 61 67 73 29 3b 0a 2b 09 72 61 77 5f 73 70 69 6e |ags);.+.raw_spin|
> 00000810 5f 75 6e 6c 6f 63 6b 5f 69 72 71 72 65 73 74 6f |_unlock_irqresto|
> 00000820 72 65 28 26 70 6d 75 5f 6c 6f 63 6b 2c 20 66 6c |re(&pmu_lock, fl|
> 00000830 61 67 73 29 3b 0a 20 7d 0a 20 0a 20 73 74 61 74 |ags);. }. . stat|
>
> So it looks like tabs (ascii code 0x09) are being converted to =09 somewhere
> on your end. Mutt should be fine, what are you connecting it to?
I'm getting the email from gmail but if I use "show original" in the gmail web
interface then it has the "=09"'s scattered through it. Your hw_breakpoint
patches seem fine though so I'm not sure what's different.
Jamie
prev parent reply other threads:[~2010-12-01 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 17:17 [PATCH] ARM: perf: use raw_spinlock_t for pmu_lock Will Deacon
2010-12-01 16:35 ` Jamie Iles
2010-12-01 16:45 ` Will Deacon
2010-12-01 17:21 ` Russell King - ARM Linux
2010-12-01 17:23 ` Jamie Iles [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=20101201172318.GG2898@pulham.picochip.com \
--to=jamie@jamieiles.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.