From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] SA11x0 fixes
Date: Fri, 3 Feb 2012 19:15:28 +0000 [thread overview]
Message-ID: <20120203191528.GE14129@n2100.arm.linux.org.uk> (raw)
This series of three patches fix a number of issues I've noticed while
looking at the SA11x0 code - they're all trivial in nature, so I don't
think too much additional explaination is required.
arch/arm/common/sa1111.c | 2 +-
arch/arm/mach-sa1100/generic.c | 4 ++--
arch/arm/mach-sa1100/hackkit.c | 2 +-
arch/arm/mach-sa1100/jornada720.c | 8 ++++----
arch/arm/mach-sa1100/sleep.S | 37 ++++++++++++++++++++++---------------
5 files changed, 30 insertions(+), 23 deletions(-)
next reply other threads:[~2012-02-03 19:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 19:15 Russell King - ARM Linux [this message]
2012-02-03 19:15 ` [PATCH 1/3] ARM: sa11x0: fix off-by-one resource sizes Russell King - ARM Linux
2012-02-03 19:16 ` [PATCH 2/3] ARM: sa11x0: fix sleep entry Russell King - ARM Linux
2012-02-03 19:16 ` [PATCH 3/3] ARM: sa11x0: fix section mismatch warnings 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=20120203191528.GE14129@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).