All of lore.kernel.org
 help / color / mirror / Atom feed
From: ao2@ao2.it (Antonio Ospite)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: lib/lib1funcs.S: fix typo s/substractions/subtractions/
Date: Thu, 28 Jan 2016 10:58:24 +0100	[thread overview]
Message-ID: <20160128105824.d04860f1b98afcdca46a29c0@ao2.it> (raw)
In-Reply-To: <20160127192711.GE10826@n2100.arm.linux.org.uk>

On Wed, 27 Jan 2016 19:27:12 +0000
Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:

> 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?

Hi Russel, can't you pick it up in the ARM tree?

I had sent this change to the trivial tree last April, and you ACKed it
back then as well, but it was not merged. Maybe Jiri, who maintains the
trivial tree, thought that you were picking it up.

I have been told, by Mark Brown IIRC, that (I'm paraphrasing) subsystem
maintainers should be the preferred recipients, and that "all-over"
maintainers are only for when the same change applies to multiple
subsystems and it does not make sense to split the patch.

Thanks,
   Antonio

-- 
Antonio Ospite
http://ao2.it

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?

      reply	other threads:[~2016-01-28  9:58 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
2016-01-28  9:58   ` Antonio Ospite [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=20160128105824.d04860f1b98afcdca46a29c0@ao2.it \
    --to=ao2@ao2.it \
    --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.