linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Burton <paulburton@kernel.org>
To: Alexander Lobakin <alobakin@dlink.ru>
Cc: Paul Burton <paulburton@kernel.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
	James Hogan <jhogan@kernel.org>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	Rob Herring <robh@kernel.org>,
	Alexander Lobakin <alobakin@dlink.ru>,
	linux-mips@vger.kernel.org, stable@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: linux-mips@vger.kernel.org
Subject: Re: [PATCH mips-fixes 0/3] MIPS: a set of tiny Kbuild fixes
Date: Tue, 21 Jan 2020 13:37:17 -0800	[thread overview]
Message-ID: <5e276f0e.1c69fb81.7e73d.180a@mx.google.com> (raw)
In-Reply-To: <20200117140209.17672-1-alobakin@dlink.ru>

Hello,

Alexander Lobakin wrote:
> These three fix two command output messages and a typo which leads
> to constant rebuild of vmlinux.lzma.its and all dependants on every
> make invocation.
> Nothing critical, and can be backported without manual intervention.
> 
> Alexander Lobakin (3):
>   MIPS: fix indentation of the 'RELOCS' message
>   MIPS: boot: fix typo in 'vmlinux.lzma.its' target
>   MIPS: syscalls: fix indentation of the 'SYSNR' message
> 
>  arch/mips/Makefile.postlink        | 2 +-
>  arch/mips/boot/Makefile            | 2 +-
>  arch/mips/kernel/syscalls/Makefile | 2 +-

Series applied to mips-next.

> MIPS: fix indentation of the 'RELOCS' message
>   commit a53998802e17
>   https://git.kernel.org/mips/c/a53998802e17
>   
>   Fixes: 44079d3509ae ("MIPS: Use Makefile.postlink to insert relocations into vmlinux")
>   Signed-off-by: Alexander Lobakin <alobakin@dlink.ru>
>   [paulburton@kernel.org: Fixup commit references in commit message.]
>   Signed-off-by: Paul Burton <paulburton@kernel.org>
> 
> MIPS: boot: fix typo in 'vmlinux.lzma.its' target
>   commit 16202c09577f
>   https://git.kernel.org/mips/c/16202c09577f
>   
>   Fixes: 92b34a976348 ("MIPS: boot: add missing targets for vmlinux.*.its")
>   Signed-off-by: Alexander Lobakin <alobakin@dlink.ru>
>   [paulburton@kernel.org: s/invokation/invocation/]
>   Signed-off-by: Paul Burton <paulburton@kernel.org>
> 
> MIPS: syscalls: fix indentation of the 'SYSNR' message
>   commit 4f29ad200f7b
>   https://git.kernel.org/mips/c/4f29ad200f7b
>   
>   Fixes: 9bcbf97c6293 ("mips: add system call table generation support")
>   Signed-off-by: Alexander Lobakin <alobakin@dlink.ru>
>   Signed-off-by: Paul Burton <paulburton@kernel.org>

Thanks,
    Paul

[ This message was auto-generated; if you believe anything is incorrect
  then please email paulburton@kernel.org to report it. ]

  parent reply	other threads:[~2020-01-21 21:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-17 14:02 [PATCH mips-fixes 0/3] MIPS: a set of tiny Kbuild fixes Alexander Lobakin
2020-01-17 14:02 ` [PATCH mips-fixes 1/3] MIPS: fix indentation of the 'RELOCS' message Alexander Lobakin
2020-01-17 14:02 ` [PATCH mips-fixes 2/3] MIPS: boot: fix typo in 'vmlinux.lzma.its' target Alexander Lobakin
2020-01-17 14:02 ` [PATCH mips-fixes 3/3] MIPS: syscalls: fix indentation of the 'SYSNR' message Alexander Lobakin
2020-01-21 21:37 ` Paul Burton [this message]
2020-01-22  8:02   ` [PATCH mips-fixes 0/3] MIPS: a set of tiny Kbuild fixes Alexander Lobakin

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=5e276f0e.1c69fb81.7e73d.180a@mx.google.com \
    --to=paulburton@kernel.org \
    --cc=alobakin@dlink.ru \
    /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).