public inbox for linux-mips@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Lobakin <alobakin@dlink.ru>
To: 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
Subject: [PATCH mips-fixes 0/3] MIPS: a set of tiny Kbuild fixes
Date: Fri, 17 Jan 2020 17:02:06 +0300	[thread overview]
Message-ID: <20200117140209.17672-1-alobakin@dlink.ru> (raw)

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 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

-- 
2.25.0


             reply	other threads:[~2020-01-17 14:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-17 14:02 Alexander Lobakin [this message]
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 ` [PATCH mips-fixes 0/3] MIPS: a set of tiny Kbuild fixes Paul Burton
2020-01-22  8:02   ` 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=20200117140209.17672-1-alobakin@dlink.ru \
    --to=alobakin@dlink.ru \
    --cc=jhogan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=paulburton@kernel.org \
    --cc=ralf@linux-mips.org \
    --cc=robh@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=yamada.masahiro@socionext.com \
    /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