From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: lib/lib1funcs.S: fix typo s/substractions/subtractions/
Date: Wed, 27 Jan 2016 19:27:12 +0000 [thread overview]
Message-ID: <20160127192711.GE10826@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1453902670-32294-1-git-send-email-ao2@ao2.it>
On Wed, Jan 27, 2016 at 02:51:10PM +0100, Antonio Ospite wrote:
> While at it also fix some other typos in the affected lines:
> s/reminder/remainder/
> s/comparison/comparisons/
>
> Signed-off-by: Antonio Ospite <ao2@ao2.it>
Acked-by: Russell King <rmk+kernel@Arm.linux.org.uk>
Thanks. I assume the trivial tree will be picking this up?
--
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2016-01-27 19:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 13:51 [PATCH] ARM: lib/lib1funcs.S: fix typo s/substractions/subtractions/ Antonio Ospite
2016-01-27 19:27 ` Russell King - ARM Linux [this message]
2016-01-28 9:58 ` Antonio Ospite
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=20160127192711.GE10826@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).