From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-mips <linux-mips@vger.kernel.org>
Subject: [GIT PULL] MIPS fixes for v5.6
Date: Wed, 11 Mar 2020 11:11:55 +0100 [thread overview]
Message-ID: <20200311101155.GA9476@alpha.franken.de> (raw)
Hi Linus,
here are some small MIPS fixes for v5.6. Please pull.
Thomas.
The following changes since commit 3234f4ed3066a58cd5ce8edcf752fa4fe0c95cb5:
MAINTAINERS: Hand MIPS over to Thomas (2020-02-24 22:43:18 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git tags/mips_fixes_5.6.1
for you to fetch changes up to f7d5f5655ef7e5d2a128f6696ac35256e83b119b:
MAINTAINERS: Correct MIPS patchwork URL (2020-03-09 12:10:01 +0100)
----------------------------------------------------------------
A few MIPS fixes:
- DT fixes for CI20
- Fix command line handling
- Correct patchwork URL
----------------------------------------------------------------
H. Nikolaus Schaller (2):
MIPS: DTS: CI20: fix PMU definitions for ACT8600
MIPS: DTS: CI20: fix interrupt for pcf8563 RTC
Paul Cercueil (1):
MIPS: Fix CONFIG_MIPS_CMDLINE_DTB_EXTEND handling
Thomas Bogendoerfer (1):
MAINTAINERS: Correct MIPS patchwork URL
MAINTAINERS | 2 +-
arch/mips/boot/dts/ingenic/ci20.dts | 44 +++++++++++++++++++++++--------------
arch/mips/kernel/setup.c | 3 ++-
3 files changed, 31 insertions(+), 18 deletions(-)
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next reply other threads:[~2020-03-11 10:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 10:11 Thomas Bogendoerfer [this message]
2020-03-11 20:45 ` [GIT PULL] MIPS fixes for v5.6 pr-tracker-bot
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=20200311101155.GA9476@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=torvalds@linux-foundation.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).